Skip to content

Harden bounded process execution and enable hosted v1alpha1 RC gates - #1

Merged
Ompragash merged 18 commits into
mainfrom
codex/hosted-ci-rc-hardening
Jul 22, 2026
Merged

Harden bounded process execution and enable hosted v1alpha1 RC gates#1
Ompragash merged 18 commits into
mainfrom
codex/hosted-ci-rc-hardening

Conversation

@Ompragash

Copy link
Copy Markdown
Contributor

Summary

  • Bound shell-action stdout, stderr, and combined capture with validated workflow/pack limits, concurrent draining, termination/reaping, secret-safe diagnostics, and durable timeout/cancellation semantics.
  • Bound repository acceptance/container command capture while preserving parseable JSON behavior.
  • Add automatic Linux x64, macOS arm64, Windows x64, container, dependency, complete-history/tree secret, workflow-lint, package, vulnerability, and SBOM gates.
  • Pin every external action to a reviewed full commit SHA with an exact-version comment.
  • Add an optional build-only CA secret mount without disabling TLS or retaining the CA in image layers/history.
  • Document the hosted handoff, required checks, artifacts, digests, and release procedure.

Local verification

  • cargo xtask verify
  • cargo xtask acceptance
  • cargo xtask package
  • AGENTCTL_BUILD_CA_FILE=<protected-public-CA-bundle> cargo xtask acceptance-container
  • actionlint 1.7.12: passed
  • Gitleaks 8.30.1 complete history and current tracked tree: no findings; synthetic credential: detected
  • Trivy 0.72.0: zero fixed HIGH/CRITICAL findings; CycloneDX image SBOM validated

All credential-free gates were run with provider credential variables removed. No live provider call was made. .release-evidence was not read, modified, staged, scanned as tree content, or uploaded.

Hosted validation required

This PR configures hosted validation but does not claim it has run. Before RC promotion, require the three platform gates, production SBOM, container, and supply-chain checks; verify every uploaded package/SBOM digest; then manually dispatch rc-release-preparation for the exact candidate commit.

Risk and review focus

  • Subprocess termination and simultaneous stdout/stderr pressure.
  • Failed-versus-uncertain durable effect classification.
  • Windows compilation and acceptance behavior.
  • Action/Syft/Trivy/Gitleaks version and SHA review.
  • Optional CA cleanup and absence from build history/artifacts.
  • No accidental .release-evidence artifact inclusion.

@Ompragash
Ompragash marked this pull request as ready for review July 22, 2026 22:37
@Ompragash
Ompragash merged commit 29452db into main Jul 22, 2026
4 of 10 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