Skip to content

Establish full Bash, OS, strict-option, and supply-chain release gates #234

Description

@codeforester

Parent: #214

Train position: 20 of 26
Phase: P3 — Ecosystem trust and broad adoption

Problem

The repository has excellent tests, but the full suite runs only on current macOS and Ubuntu Bash while exact Bash 4.2 receives a narrow logging smoke. Warning lint and several release, workflow, concurrency, and adversarial guarantees are not required merge gates.

Acceptance criteria

  • Publish a support matrix and run the complete applicable suite on exact Bash 4.2, representative 4.x and 5.x releases, current Bash, Linux/glibc, Alpine/musl, and macOS/BSD userland.
  • Exercise default and supported strict-option combinations against source-installed, Homebrew-installed, vendored, generated-module, and standalone-bundled artifacts.
  • Make warning-level ShellCheck, shfmt, action and workflow lint, API and module-manifest checks, documentation examples, generated-artifact drift, and release invariants required.
  • Add deterministic property or fuzz coverage for argv, quoting, paths, parser schemas, marker handling, imports, and generated artifacts with reproducible seeds.
  • Add focused concurrency, signal, process-tree, cleanup, filesystem-race, and bounded startup/import/performance regressions.
  • Pin actions, images, and build tools; use least-privilege permissions and networkless or read-only jobs where applicable.
  • Require the complete quality workflow and approving review in default-branch protection, with documented emergency procedures that remain auditable.

Dependencies

Metadata

Metadata

Assignees

Labels

ciContinuous integration, tests, automation, or release workflows

Type

No type

Projects

Status
Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions