Status: policy
Regular implementation commits are allowed locally. Pushes are left to the maintainer. Tags are never created or pushed unless explicitly requested.
- Confirm the version scope in
docs/VERSION_PLAN.md. - Finish the version deliverables.
- Run
scripts/checks.sh. - Run
cargo deny check. - Run
cargo audit. - Run the version gate script when one exists, such as
scripts/release_0_7_gate.sh. - Run rootless Podman smoke if the milestone includes container support and it is not already covered by the version gate.
- Stop and call out the pentest handoff for the exact commit.
Use this handoff text:
vX.Y.Z is ready for pentest. Test this exact commit before release preparation.
Do not tag at this stop.
- The maintainer writes temporary findings to root
PENTEST.md. - Read
PENTEST.mdcompletely. - Fix release-scope findings.
- Update tests, docs, and release notes as needed.
- Remove
PENTEST.md. - Run
scripts/checks.sh,cargo deny check, andcargo auditagain. - Repeat if a new
PENTEST.mdis provided. - When the maintainer reports the pentest is green, write or update the
permanent digest at
security/pentest/<tag>.md. - Commit any final documentation-only release metadata, then commit the permanent pentest digest alone as required by the readiness gate. Record the exact externally retested implementation commit separately when the digest's parent includes locally reviewed documentation-only preparation. Source, dependency, tooling or workflow changes require renewed relevant verification and must not be presented as documentation-only preparation.
- Wait for GitHub Actions.
- If GitHub Actions are green, the maintainer tells Codex.
- Codex verifies the local branch is clean and tags only when explicitly instructed.
- Tags are signed when signing is available in the local Git configuration.
- Codex pushes only the tag when explicitly instructed.
- If GitHub Actions fail, the maintainer shares the failure. Codex fixes the issue, updates the permanent pentest digest if the fix changes the release evidence, commits again, and the project waits for GitHub Actions again.
No release tag is created before both pentest and GitHub Actions are green. Normal development commits may continue between versions, but a version tag is only a clean stop after the above loop completes.