This page documents the local public release gate orchestration command after the first GitHub and NuGet publication.
The gate script wraps existing checks:
scripts/check-package-metadata.ps1scripts/audit-public-release.ps1scripts/check-release-blockers.ps1
- GitHub repository public: yes.
masterpushed: yes.v0.2.0-alpha.4tag pushed: yes.- Package metadata URLs are final and should pass the metadata gate.
- GitHub Release page: completed.
- NuGet publish: completed.
- NuGet global tool install verification: completed.
- GitHub Actions latest
masterrun is green for the pushed release commit. - Repository description and topics are set.
- Codex for OSS application pack is ready.
Remote tag, GitHub Release, and NuGet package availability are external checks. The local gate scripts do not push, create releases, or publish packages.
Run:
powershell -ExecutionPolicy Bypass -File scripts/check-public-release-gates.ps1Report-only mode keeps underlying checks non-failing and exits 0 when the scripts complete, while still printing notes.
Run before future public release announcements or follow-up release work:
powershell -ExecutionPolicy Bypass -File scripts/check-public-release-gates.ps1 -FailOnIssuesIn the published 0.2.0-alpha.4 state, this gate should pass when the working tree is clean, package metadata is final, no tracked artifacts are present, and the release tag exists locally.
This script does not:
- Push commits.
- Create or push tags.
- Create GitHub Releases.
- Create remotes.
- Publish NuGet packages.
- Replace package metadata URLs.
- Redact or delete files.
Follow MAINTAINER_RELEASE_HANDOFF.md for the published release status and future maintainer-only release steps.