@eslint-sh/eslint-plugin 0.6.0 → 0.8.0

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.

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

@@ -1,6 +1,6 @@
 # `sh/compat/no-globstar`
 
-Disallow `shopt -s globstar` in scripts whose target shell lacks the option: Bash older than 4.0,
+Disallow `shopt -s globstar` in scripts that must support a shell lacking the option: 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 `find`, for example `find dir -name '*.txt'`.
 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 `shopt`.
+- `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 `shopt`.
 - `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-globstar': '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": 1} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 1} -->
 ```sh
 shopt -s nullglob globstar
 for f in src/**/*.sh; do lint "$f"; done
@@ -51,19 +51,19 @@ for f in src/**/*.sh; do lint "$f"; done
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 find src -name '*.sh' -exec lint {} \;
 shopt -s nullglob
 ```
 
-With `shellVersion: "4.0"` or newer, or with no `shellVersion`, `globstar` is fine.
+With `minBashVersion: "4.0"` or newer, or with no `minBashVersion`, `globstar` is 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
@@ -71,4 +71,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 `shopt` 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 `globstar` for a Bash 3.2 target. This rule exists for that target.
+shellcheck reports `shopt` 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 `globstar` for a script that must support Bash 3.2. This rule checks that support requirement.

package/docs/rules/compat/no-lastpipe-semantics.md

@@ -1,6 +1,6 @@
 # `sh/compat/no-lastpipe-semantics`
 
-Disallow `shopt -s lastpipe` in scripts whose target shell lacks the option: Bash older than 4.2,
+Disallow `shopt -s lastpipe` in scripts that must support a shell lacking the option: Bash older than 4.2,
 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 process substitution: `while read -r line; do …; d
 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`.
+- `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.
 - `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-lastpipe-semantics': '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": 1} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2", "findings": 1} -->
 ```sh
 shopt -s lastpipe
 cmd | while read -r line; do total=$line; done
@@ -51,23 +51,23 @@ cmd | while read -r line; do total=$line; done
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 while read -r line; do total=$line; done < <(cmd)
 ```
 
-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 warns that variables assigned in the last pipeline element are lost (SC2030/SC2031), and understands `shopt -s lastpipe` for that purpose, but it cannot target a Bash version, so it cannot report the option for a Bash 3.2 target. This rule exists for that target.
+shellcheck warns that variables assigned in the last pipeline element are lost (SC2030/SC2031), and understands `shopt -s lastpipe` for that purpose, but it cannot check support for a minimum Bash version, so it cannot report the option for a script that must support Bash 3.2. This rule checks that support requirement.

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

@@ -27,12 +27,12 @@ The portable alternative is arithmetic expansion, `n=$((1 + 2))`. The rule offer
 
 This is a POSIX-only gate. Every Bash has `let`, 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-mapfile.md

@@ -1,6 +1,6 @@
 # `sh/compat/no-mapfile`
 
-Disallow the `mapfile` builtin and its synonym `readarray` in scripts whose target shell lacks
+Disallow the `mapfile` builtin and its synonym `readarray` 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 |
@@ -16,9 +16,9 @@ never filled.
 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.
 
 The rule reports every command whose effective command is `mapfile` or `readarray`, after
@@ -31,7 +31,7 @@ For `mapfile -t NAME` or `readarray -t NAME`, written directly (no wrapper and n
 `VAR=value`) in a Bash or Bats file, the rule suggests a `while IFS= read -r` loop that fills
 the same array the same way:
 
-<!-- transform: {"kind": "suggestion", "dialect": "bash", "shellVersion": "3.2"} -->
+<!-- transform: {"kind": "suggestion", "dialect": "bash", "minBashVersion": "3.2"} -->
 
 ```sh
 mapfile -t lines < in.txt
@@ -57,12 +57,12 @@ assignment, a wrapper, and every file under `dialect: "posix"`.
 
 ## 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-mapfile': 'error',
   },
@@ -73,9 +73,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
 mapfile -t lines < in.txt          # mapfile needs Bash 4.0
 git ls-files | readarray -t files  # readarray is the same builtin
@@ -84,9 +84,9 @@ command mapfile -t lines < in.txt  # reached through the command wrapper
 
 ### Correct
 
-With `shellVersion: "3.2"`:
+With `minBashVersion: "3.2"`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "3.2"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "3.2"} -->
 ```sh
 { lines=(); while IFS= read -r || [ -n "$REPLY" ]; do lines+=("$REPLY"); done; } < in.txt
 
@@ -95,16 +95,16 @@ while IFS= read -r line; do
 done < in.txt
 ```
 
-With `shellVersion: "4.0"` or newer, or with no `shellVersion`:
+With `minBashVersion: "4.0"` or newer, or with no `minBashVersion`:
 
-<!-- example: {"dialect": "bash", "shellVersion": "4.0"} -->
+<!-- example: {"dialect": "bash", "minBashVersion": "4.0"} -->
 ```sh
 mapfile -t lines < in.txt
 ```
 
 ## 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
@@ -113,6 +113,6 @@ eslint-sh is a convention and contract linter: a policy layer, where shellcheck
 layer. Run shellcheck beside it.
 
 shellcheck reports Bash-only features in scripts it treats as POSIX sh (the SC3xxx checks), but
-it cannot target a Bash version, so it cannot report `mapfile` in a script that must run on
+it cannot check support for a minimum Bash version, so it cannot report `mapfile` in a script that must run on
 Bash 3.2. shellcheck 0.11.0 does recommend `mapfile` or `read -a` over `a=($(cmd))` splitting (SC2207) under `-s bash`, which is
-the opposite advice for a Bash 3.2 target. This rule exists for that target.
+the opposite advice for a script that must support Bash 3.2. This rule checks that support requirement.