Skip to content

ext-tool join: fail loudly when SCRIPT_DIR is unset - #1730

Merged
fujibee merged 1 commit into
integration/plugin-installfrom
fix/plugin-env-read-gate
Oct 23, 2026
Merged

fujibee merged 1 commit into
integration/plugin-installfrom
fix/plugin-env-read-gate

Conversation

@fujibee

@fujibee fujibee commented Oct 23, 2026

Copy link
Copy Markdown
Owner

On top of 1.6.0, check-unguarded-env-reads counts 61 against a baseline of 60. The new row is the driver-registry source in scripts/drivers/types/ext-tool/_join.sh, added for plugin-sourced ext-tools (#1700).

This reads it as ${SCRIPT_DIR:?}, so a missing value stops with a named error rather than a bare set -u abort.

Verified:

  • .github/scripts/check-unguarded-env-reads.sh: 60, at the baseline
  • tests/test_unguarded_env_reads.bats and the ext-tool suites: 365/365

The driver-registry source added for plugin-sourced ext-tools read
SCRIPT_DIR with no guard, which put check-unguarded-env-reads one over
its baseline (61/60) once the branch sat on 1.6.0. Use ${SCRIPT_DIR:?}
so a missing value stops with a named error instead of a bare set -u
abort, and the count is back at the baseline.
@fujibee
fujibee merged commit 8928f6f into integration/plugin-install Oct 23, 2026
10 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant