@eslint-sh/eslint-plugin 0.7.0 → 0.8.0

package/docs/rules/compat/no-brace-sequence-padding-step.md

@@ -28,19 +28,19 @@ The portable alternative is to count in a loop and format with `printf`, for exa
 This is a version-compat rule. Whether it reports depends only on `languageOptions`, as
 described in [version compatibility](../../compat.md):
 
-- `shellVersion` unset: never reports. An unset version means the newest Bash.
-- `dialect: "bash"` (the default) or `"bats"`: reports when `shellVersion` is older than `4.0`.
-- `dialect: "posix"`: reports at any `shellVersion`, because POSIX does not specify brace expansion.
+- `minBashVersion` unset: no Bash version constraint, so no report under `bash` or `bats`.
+- `dialect: "bash"` (the default) or `"bats"`: reports when `minBashVersion` is older than `4.0`.
+- `dialect: "posix"`: reports regardless of Bash releases, because POSIX does not specify brace expansion.
 - `dialect: "mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js
 {
-  languageOptions: { dialect: 'bash', shellVersion: '3.2' },
+  languageOptions: { dialect: 'bash', minBashVersion: '3.2' },
   rules: {
     'sh/compat/no-brace-sequence-padding-step': 'error',
   },
@@ -51,9 +51,9 @@ This rule has no options. Set the target through `languageOptions`:
 
 ### Incorrect
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2", "findings": 3} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 3} -->
 
 ```sh
 for n in {01..12}; do echo "report-$n"; done
@@ -63,9 +63,9 @@ cp backup{a..e..2}.tar /tmp
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 
 ```sh
 n=1
@@ -75,11 +75,11 @@ echo '{01..12}'
 a={01..03}
 ```
 
-With `shellVersion: "4.0"` or newer, or with no `shellVersion`, both forms are fine.
+With `minBashVersion: "4.0"` or newer, or with no `minBashVersion`, both forms are fine.
 
 ## When not to use it
 
-Turn the rule off when your scripts never run on Bash older than 4.0, or leave `shellVersion`
+Turn the rule off when your scripts never run on Bash older than 4.0, or leave `minBashVersion`
 unset, which makes the rule report nothing.
 
 ## Relationship to shellcheck
@@ -87,4 +87,4 @@ unset, which makes the rule report nothing.
 eslint-sh is a convention and contract linter: a policy layer, where shellcheck is the gotcha
 layer. Run shellcheck beside it.
 
-shellcheck 0.11.0 reports SC3009 (brace expansion is undefined in POSIX sh) under `-s sh` for every brace expansion, a plain `{1..3}` and `{a,b}` included. Under `-s bash` it reports nothing for these sequences. It does not know which Bash release a script must run on, so it cannot report the padded and stepped forms for a Bash 3.2 target. This rule exists for that target.
+shellcheck 0.11.0 reports SC3009 (brace expansion is undefined in POSIX sh) under `-s sh` for every brace expansion, a plain `{1..3}` and `{a,b}` included. Under `-s bash` it reports nothing for these sequences. It does not know which Bash release a script must run on, so it cannot report the padded and stepped forms for a script that must support Bash 3.2. This rule checks that support requirement.

package/docs/rules/compat/no-case-attributes.md

@@ -1,7 +1,7 @@
 # `sh/compat/no-case-attributes`
 
 Disallow the case-converting attributes `declare -l` and `declare -u` (also through `typeset` and
-`local`) in scripts whose target shell lacks them: Bash older than 4.0, including the Bash 3.2
+`local`) in scripts that must support a shell lacking them: Bash older than 4.0, including the Bash 3.2
 that macOS ships as `/bin/bash`, and POSIX sh.
 
 | Configs                      | Fixable     | Languages |
@@ -19,19 +19,19 @@ The portable alternative is to convert the value when it is assigned, with `tr`:
 This is a version-compat rule. Whether it reports depends only on `languageOptions`, as
 described in [version compatibility](../../compat.md):
 
-- `shellVersion` unset: never reports. An unset version means the newest Bash.
-- `dialect: "bash"` (the default) or `"bats"`: reports when `shellVersion` is older than `4.0`.
-- `dialect: "posix"`: reports at any `shellVersion`, because POSIX sh has no `declare`.
+- `minBashVersion` unset: no Bash version constraint, so no report under `bash` or `bats`.
+- `dialect: "bash"` (the default) or `"bats"`: reports when `minBashVersion` is older than `4.0`.
+- `dialect: "posix"`: reports regardless of Bash releases, because POSIX sh has no `declare`.
 - `dialect: "mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js
 {
-  languageOptions: { dialect: 'bash', shellVersion: '3.2' },
+  languageOptions: { dialect: 'bash', minBashVersion: '3.2' },
   rules: {
     'sh/compat/no-case-attributes': 'error',
   },
@@ -42,9 +42,9 @@ This rule has no options. Set the target through `languageOptions`:
 
 ### Incorrect
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2", "findings": 2} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 2} -->
 
 ```sh
 declare -l answer=$1
@@ -55,9 +55,9 @@ f() {
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 
 ```sh
 answer=$(printf '%s' "$1" | tr '[:upper:]' '[:lower:]')
@@ -67,11 +67,11 @@ f() {
 }
 ```
 
-With `shellVersion: "4.0"` or newer, or with no `shellVersion`, the attributes are fine.
+With `minBashVersion: "4.0"` or newer, or with no `minBashVersion`, the attributes are fine.
 
 ## When not to use it
 
-Turn the rule off when your scripts never run on Bash older than 4.0, or leave `shellVersion`
+Turn the rule off when your scripts never run on Bash older than 4.0, or leave `minBashVersion`
 unset, which makes the rule report nothing.
 
 ## Relationship to shellcheck
@@ -79,4 +79,4 @@ unset, which makes the rule report nothing.
 eslint-sh is a convention and contract linter: a policy layer, where shellcheck is the gotcha
 layer. Run shellcheck beside it.
 
-Under `-s sh`, shellcheck 0.11.0 reports the command, not the option: `declare -l` and `declare -u` draw SC3044 (`declare` is undefined in POSIX sh), and `local -l` and `local -u` draw SC3043. Under `-s bash` it reports nothing for these options. It does not know which Bash release a script must run on, so it reports nothing for `declare -l` in a Bash 3.2 target. This rule exists for that target.
+Under `-s sh`, shellcheck 0.11.0 reports the command, not the option: `declare -l` and `declare -u` draw SC3044 (`declare` is undefined in POSIX sh), and `local -l` and `local -u` draw SC3043. Under `-s bash` it reports nothing for these options. It does not know which Bash release a script must run on, so it reports nothing for `declare -l` in a script that must support Bash 3.2. This rule checks that support requirement.

package/docs/rules/compat/no-case-fallthrough.md

@@ -1,7 +1,7 @@
 # `sh/compat/no-case-fallthrough`
 
 Disallow the `case` terminators `;&` (run the next branch without testing its pattern) and `;;&`
-(go on testing the next patterns) in scripts whose target shell lacks them: Bash older than 4.0,
+(go on testing the next patterns) in scripts that must support a shell lacking them: Bash older than 4.0,
 including the Bash 3.2 that macOS ships as `/bin/bash`, and POSIX sh.
 
 | Configs | Fixable | Languages |
@@ -21,18 +21,18 @@ Under `dialect: "posix"` the parser itself rejects both terminators, so a POSIX
 This is a version-compat rule. Whether it reports depends only on `languageOptions`, as
 described in [version compatibility](../../compat.md):
 
-- `shellVersion` unset: never reports. An unset version means the newest Bash.
-- `dialect: "bash"` (the default) or `"bats"`: reports when `shellVersion` is older than `4.0`.
+- `minBashVersion` unset: no Bash version constraint, so no report under `bash` or `bats`.
+- `dialect: "bash"` (the default) or `"bats"`: reports when `minBashVersion` is older than `4.0`.
 - `dialect: "mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js
 {
-  languageOptions: { dialect: 'bash', shellVersion: '3.2' },
+  languageOptions: { dialect: 'bash', minBashVersion: '3.2' },
   rules: {
     'sh/compat/no-case-fallthrough': 'error',
   },
@@ -43,9 +43,9 @@ This rule has no options. Set the target through `languageOptions`:
 
 ### Incorrect
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2", "findings": 2} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 2} -->
 ```sh
 case $level in
   debug) verbose=1 ;&
@@ -59,9 +59,9 @@ esac
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 case $level in
   debug) verbose=1; log=1 ;;
@@ -75,11 +75,11 @@ case $file in
 esac
 ```
 
-With `shellVersion: "4.0"` or newer, or with no `shellVersion`, both terminators are fine.
+With `minBashVersion: "4.0"` or newer, or with no `minBashVersion`, both terminators are fine.
 
 ## When not to use it
 
-Turn the rule off when your scripts never run on Bash older than 4.0, or leave `shellVersion`
+Turn the rule off when your scripts never run on Bash older than 4.0, or leave `minBashVersion`
 unset, which makes the rule report nothing.
 
 ## Relationship to shellcheck
@@ -87,4 +87,4 @@ unset, which makes the rule report nothing.
 eslint-sh is a convention and contract linter: a policy layer, where shellcheck is the gotcha
 layer. Run shellcheck beside it.
 
-Under `-s sh`, shellcheck 0.11.0 reports `;&` and `;;&` as an error, SC2127 ("To use cases with ;&, specify #!/usr/bin/env bash or ksh", or the `;;&` equivalent naming bash), not as one of its SC3xxx portability checks. It reports the same SC2127 under `-s dash`, reports `;;&` (but not `;&`) under `-s ksh`, and reports nothing under `-s bash`. It does not know which Bash release a script must run on, so it reports nothing for either operator in a Bash 3.2 target. This rule exists for that target.
+Under `-s sh`, shellcheck 0.11.0 reports `;&` and `;;&` as an error, SC2127 ("To use cases with ;&, specify #!/usr/bin/env bash or ksh", or the `;;&` equivalent naming bash), not as one of its SC3xxx portability checks. It reports the same SC2127 under `-s dash`, reports `;;&` (but not `;&`) under `-s ksh`, and reports nothing under `-s bash`. It does not know which Bash release a script must run on, so it reports nothing for either operator in a script that must support Bash 3.2. This rule checks that support requirement.

package/docs/rules/compat/no-case-modification.md

@@ -17,19 +17,19 @@ The report is on the whole expansion, with or without a trailing pattern (`${v^^
 This is a version-compat rule. Whether it reports depends only on `languageOptions`, as
 described in [version compatibility](../../compat.md):
 
-- `shellVersion` unset: never reports. An unset version means the newest Bash.
-- `dialect: "bash"` (the default) or `"bats"`: reports when `shellVersion` is older than `4.0`.
+- `minBashVersion` unset: no Bash version constraint, so no report under `bash` or `bats`.
+- `dialect: "bash"` (the default) or `"bats"`: reports when `minBashVersion` is older than `4.0`.
 - `dialect: "posix"`: reports nothing in practice for this syntax, because the POSIX parser rejects it with a parse error before any rule runs.
 - `dialect: "mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js
 {
-  languageOptions: { dialect: 'bash', shellVersion: '3.2' },
+  languageOptions: { dialect: 'bash', minBashVersion: '3.2' },
   rules: {
     'sh/compat/no-case-modification': 'error',
   },
@@ -40,9 +40,9 @@ This rule has no options. Set the target through `languageOptions`:
 
 ### Incorrect
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2", "findings": 3} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 3} -->
 ```sh
 name=${input,,}      # lowercase every character
 title=${word^}       # uppercase the first character
@@ -51,24 +51,24 @@ flag=${arg^^[a-z]}   # with a pattern
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 name=$(printf '%s' "$input" | tr '[:upper:]' '[:lower:]')
 title=$(printf '%s' "${word%"${word#?}"}" | tr '[:lower:]' '[:upper:]')"${word#?}"
 ```
 
-With `shellVersion: "4.0"` or newer, or with no `shellVersion`, the original forms are fine.
+With `minBashVersion: "4.0"` or newer, or with no `minBashVersion`, the original forms are fine.
 
 ## When not to use it
 
 Turn the rule off when your scripts never run on Bash older than 4.0, or leave
-`shellVersion` unset, which makes the rule report nothing.
+`minBashVersion` unset, which makes the rule report nothing.
 
 ## Relationship to shellcheck
 
 eslint-sh is a convention and contract linter: a policy layer, where shellcheck is the gotcha
 layer. Run shellcheck beside it.
 
-shellcheck reports case-modifying expansions in scripts it treats as POSIX sh (SC3059), but it cannot target a Bash version, so it cannot report `${v,,}` in a script that must run on Bash 3.2. This rule exists for that target.
+shellcheck reports case-modifying expansions in scripts it treats as POSIX sh (SC3059), but it cannot check support for a minimum Bash version, so it cannot report `${v,,}` in a script that must run on Bash 3.2. This rule checks that support requirement.

package/docs/rules/compat/no-coproc.md

@@ -1,6 +1,6 @@
 # `sh/compat/no-coproc`
 
-Disallow the `coproc` reserved word in scripts whose target shell lacks it: Bash older than 4.0,
+Disallow the `coproc` reserved word in scripts that must support a shell lacking it: Bash older than 4.0,
 including the Bash 3.2 that macOS ships as `/bin/bash`, and POSIX sh.
 
 | Configs | Fixable | Languages |
@@ -18,19 +18,19 @@ The portable alternative is a named pipe: create it with `mkfifo`, start the cop
 This is a version-compat rule. Whether it reports depends only on `languageOptions`, as
 described in [version compatibility](../../compat.md):
 
-- `shellVersion` unset: never reports. An unset version means the newest Bash.
-- `dialect: "bash"` (the default) or `"bats"`: reports when `shellVersion` is older than `4.0`.
-- `dialect: "posix"`: reports at any `shellVersion`.
+- `minBashVersion` unset: no Bash version constraint, so no report under `bash` or `bats`.
+- `dialect: "bash"` (the default) or `"bats"`: reports when `minBashVersion` is older than `4.0`.
+- `dialect: "posix"`: reports regardless of Bash releases.
 - `dialect: "mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js
 {
-  languageOptions: { dialect: 'bash', shellVersion: '3.2' },
+  languageOptions: { dialect: 'bash', minBashVersion: '3.2' },
   rules: {
     'sh/compat/no-coproc': 'error',
   },
@@ -41,9 +41,9 @@ This rule has no options. Set the target through `languageOptions`:
 
 ### Incorrect
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2", "findings": 2} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 2} -->
 ```sh
 coproc worker { cat; }
 coproc sort
@@ -51,9 +51,9 @@ coproc sort
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 fifo=$(mktemp -u) && mkfifo "$fifo"
 cat < "$fifo" &
@@ -61,16 +61,16 @@ exec 3> "$fifo"
 printf '%s\n' hello >&3
 ```
 
-With `shellVersion: "4.0"` or newer, or with no `shellVersion`, the original forms are fine.
+With `minBashVersion: "4.0"` or newer, or with no `minBashVersion`, the original forms are fine.
 
 ## When not to use it
 
 Turn the rule off when your scripts never run on Bash older than 4.0, or leave
-`shellVersion` unset, which makes the rule report nothing.
+`minBashVersion` unset, which makes the rule report nothing.
 
 ## Relationship to shellcheck
 
 eslint-sh is a convention and contract linter: a policy layer, where shellcheck is the gotcha
 layer. Run shellcheck beside it.
 
-shellcheck has no check for `coproc` in a script that must run on an older Bash; it cannot target a Bash version. This rule exists for that target.
+shellcheck has no check for `coproc` in a script that must run on an older Bash; it cannot check support for a minimum Bash version. This rule checks that support requirement.

package/docs/rules/compat/no-declare-g.md

@@ -1,6 +1,6 @@
 # `sh/compat/no-declare-g`
 
-Disallow `declare -g` and `typeset -g` in scripts whose target shell lacks the `-g` option: Bash
+Disallow `declare -g` and `typeset -g` in scripts that must support a shell lacking the `-g` option: Bash
 older than 4.2, including the Bash 3.2 that macOS ships as `/bin/bash`, and POSIX sh.
 
 | Configs | Fixable | Languages |
@@ -20,19 +20,19 @@ The message says so. For a plain `-g` (and `-gx`, which `export name=value` cove
 This is a version-compat rule. Whether it reports depends only on `languageOptions`, as
 described in [version compatibility](../../compat.md):
 
-- `shellVersion` unset: never reports. An unset version means the newest Bash.
-- `dialect: "bash"` (the default) or `"bats"`: reports when `shellVersion` is older than `4.2`.
-- `dialect: "posix"`: reports at any `shellVersion`, because POSIX sh has no `declare`.
+- `minBashVersion` unset: no Bash version constraint, so no report under `bash` or `bats`.
+- `dialect: "bash"` (the default) or `"bats"`: reports when `minBashVersion` is older than `4.2`.
+- `dialect: "posix"`: reports regardless of Bash releases, because POSIX sh has no `declare`.
 - `dialect: "mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js
 {
-  languageOptions: { dialect: 'bash', shellVersion: '3.2' },
+  languageOptions: { dialect: 'bash', minBashVersion: '3.2' },
   rules: {
     'sh/compat/no-declare-g': 'error',
   },
@@ -43,9 +43,9 @@ This rule has no options. Set the target through `languageOptions`:
 
 ### Incorrect
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2", "findings": 2} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 2} -->
 ```sh
 f() {
   declare -g counter=0
@@ -55,9 +55,9 @@ f() {
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 f() {
   counter=0
@@ -65,16 +65,16 @@ f() {
 }
 ```
 
-With `shellVersion: "4.2"` or newer, or with no `shellVersion`, the original forms are fine.
+With `minBashVersion: "4.2"` or newer, or with no `minBashVersion`, the original forms are fine.
 
 ## When not to use it
 
 Turn the rule off when your scripts never run on Bash older than 4.2, or leave
-`shellVersion` unset, which makes the rule report nothing.
+`minBashVersion` unset, which makes the rule report nothing.
 
 ## Relationship to shellcheck
 
 eslint-sh is a convention and contract linter: a policy layer, where shellcheck is the gotcha
 layer. Run shellcheck beside it.
 
-shellcheck does not know which Bash a script must run on, so it cannot report `declare -g` for a Bash 3.2 target. This rule exists for that target.
+shellcheck does not know which Bash a script must run on, so it cannot report `declare -g` for a script that must support Bash 3.2. This rule checks that support requirement.

package/docs/rules/compat/no-double-bracket.md

@@ -18,12 +18,12 @@ The portable alternatives are `[ … ]` for tests and `case` for pattern matchin
 
 This is a POSIX-only gate. Every Bash has `[[`, so whether the rule reports depends only on `dialect`, as described in [version compatibility](../../compat.md):
 
-- `dialect: "posix"`: reports at any `shellVersion`.
+- `dialect: "posix"`: reports regardless of Bash releases.
 - `dialect: "bash"` (the default), `"bats"`, `"mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js

package/docs/rules/compat/no-epoch-variables.md

@@ -1,6 +1,6 @@
 # `sh/compat/no-epoch-variables`
 
-Disallow `$EPOCHSECONDS` and `$EPOCHREALTIME` in scripts whose target shell lacks them: Bash older
+Disallow `$EPOCHSECONDS` and `$EPOCHREALTIME` in scripts that must support a shell lacking them: Bash older
 than 5.0, including the Bash 3.2 that macOS ships as `/bin/bash`, and POSIX sh.
 
 | Configs | Fixable | Languages |
@@ -20,19 +20,19 @@ The usual alternative is `$(date +%s)`. It is not POSIX: `%s` is an extension th
 This is a version-compat rule. Whether it reports depends only on `languageOptions`, as
 described in [version compatibility](../../compat.md):
 
-- `shellVersion` unset: never reports. An unset version means the newest Bash.
-- `dialect: "bash"` (the default) or `"bats"`: reports when `shellVersion` is older than `5.0`.
-- `dialect: "posix"`: reports at any `shellVersion`, because POSIX sh does not set either variable.
+- `minBashVersion` unset: no Bash version constraint, so no report under `bash` or `bats`.
+- `dialect: "bash"` (the default) or `"bats"`: reports when `minBashVersion` is older than `5.0`.
+- `dialect: "posix"`: reports regardless of Bash releases, because POSIX sh does not set either variable.
 - `dialect: "mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js
 {
-  languageOptions: { dialect: 'bash', shellVersion: '3.2' },
+  languageOptions: { dialect: 'bash', minBashVersion: '3.2' },
   rules: {
     'sh/compat/no-epoch-variables': 'error',
   },
@@ -43,9 +43,9 @@ This rule has no options. Set the target through `languageOptions`:
 
 ### Incorrect
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2", "findings": 2} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 2} -->
 ```sh
 start=$EPOCHSECONDS
 run_tests
@@ -54,9 +54,9 @@ echo "took $(( EPOCHSECONDS - start ))s"
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 start=$(date +%s)
 run_tests
@@ -64,11 +64,11 @@ echo "took $(( $(date +%s) - start ))s"
 echo 'the variable is spelled $EPOCHSECONDS'
 ```
 
-With `shellVersion: "5.0"` or newer, or with no `shellVersion`, both variables are fine.
+With `minBashVersion: "5.0"` or newer, or with no `minBashVersion`, both variables are fine.
 
 ## When not to use it
 
-Turn the rule off when your scripts never run on Bash older than 5.0, or leave `shellVersion`
+Turn the rule off when your scripts never run on Bash older than 5.0, or leave `minBashVersion`
 unset, which makes the rule report nothing.
 
 ## Relationship to shellcheck
@@ -76,4 +76,4 @@ unset, which makes the rule report nothing.
 eslint-sh is a convention and contract linter: a policy layer, where shellcheck is the gotcha
 layer. Run shellcheck beside it.
 
-shellcheck 0.11.0 reports `$EPOCHSECONDS` and `$EPOCHREALTIME` as undefined in POSIX sh (SC3028) under `-s sh`, and nothing under `-s bash`. It does not know which Bash release a script must run on, so it reports nothing for either variable in a Bash 4.4 target. This rule exists for that target.
+shellcheck 0.11.0 reports `$EPOCHSECONDS` and `$EPOCHREALTIME` as undefined in POSIX sh (SC3028) under `-s sh`, and nothing under `-s bash`. It does not know which Bash release a script must run on, so it reports nothing for either variable in a script that must support Bash 4.4. This rule checks that support requirement.

package/docs/rules/compat/no-fd-variable.md

@@ -1,7 +1,7 @@
 # `sh/compat/no-fd-variable`
 
 Disallow `{varname}` redirections, which have the shell pick a free file descriptor and store its
-number in a variable (`exec {fd}>file`), in scripts whose target shell lacks them: Bash older than
+number in a variable (`exec {fd}>file`), in scripts that must support a shell lacking them: Bash older than
 4.1, including the Bash 3.2 that macOS ships as `/bin/bash`, and POSIX sh.
 
 | Configs | Fixable | Languages |
@@ -21,18 +21,18 @@ Under `dialect: "posix"` the parser itself rejects `{varname}` redirections, so
 This is a version-compat rule. Whether it reports depends only on `languageOptions`, as
 described in [version compatibility](../../compat.md):
 
-- `shellVersion` unset: never reports. An unset version means the newest Bash.
-- `dialect: "bash"` (the default) or `"bats"`: reports when `shellVersion` is older than `4.1`.
+- `minBashVersion` unset: no Bash version constraint, so no report under `bash` or `bats`.
+- `dialect: "bash"` (the default) or `"bats"`: reports when `minBashVersion` is older than `4.1`.
 - `dialect: "mksh"` or `"zsh"`: never reports.
 
 ## Options
 
-This rule has no options. Set the target through `languageOptions`:
+This rule has no options. Set the required support through `languageOptions`:
 
 ```js
 // eslint.config.js
 {
-  languageOptions: { dialect: 'bash', shellVersion: '3.2' },
+  languageOptions: { dialect: 'bash', minBashVersion: '3.2' },
   rules: {
     'sh/compat/no-fd-variable': 'error',
   },
@@ -43,9 +43,9 @@ This rule has no options. Set the target through `languageOptions`:
 
 ### Incorrect
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2", "findings": 2} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 2} -->
 ```sh
 exec {log}>>"$logfile"
 echo started >&"$log"
@@ -54,20 +54,20 @@ exec {log}>&-
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 exec 3>>"$logfile"
 echo started >&3
 exec 3>&-
 ```
 
-With `shellVersion: "4.1"` or newer, or with no `shellVersion`, `{varname}` redirections are fine.
+With `minBashVersion: "4.1"` or newer, or with no `minBashVersion`, `{varname}` redirections are fine.
 
 ## When not to use it
 
-Turn the rule off when your scripts never run on Bash older than 4.1, or leave `shellVersion`
+Turn the rule off when your scripts never run on Bash older than 4.1, or leave `minBashVersion`
 unset, which makes the rule report nothing.
 
 ## Relationship to shellcheck
@@ -75,4 +75,4 @@ unset, which makes the rule report nothing.
 eslint-sh is a convention and contract linter: a policy layer, where shellcheck is the gotcha
 layer. Run shellcheck beside it.
 
-shellcheck reports `{varname}` redirections only for a script it treats as POSIX `sh` (its SC3xxx portability checks). It does not know which Bash release a script must run on, so it cannot report them for a Bash 3.2 target. This rule exists for that target.
+shellcheck reports `{varname}` redirections only for a script it treats as POSIX `sh` (its SC3xxx portability checks). It does not know which Bash release a script must run on, so it cannot report them for a script that must support Bash 3.2. This rule checks that support requirement.