release-readiness
Use when preparing a release or release candidate, cutting a tag, or checking whether the release gates and evidence are ready.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 4
- Forks
- 2
01 前言 Front Matter
- name
- release-readiness
- license
- MIT
- description
- Use when preparing a release or release candidate, cutting a tag, or checking whether the release gates and evidence are ready.
02 资源文件 1
- 参考文档references/release-runbook.md2.9 KB
03 SKILL.md 正文
Release readiness
Outcome: every gate is green on the release commit, the schema fixture is
registered, the ASVS/MASVS obligation is discharged, and the PR/release carries
the operator notes. Read docs/development/release-gates.md and
docs/changelog-policy.md before dispatching.
Steps
- Open the release runbook and follow it in order; it links the canonical gate registry instead of copying it.
- Confirm the commit, not just the branch:
release.ymlbuilds the release commit andreleasegatecheckre-checks the composed gates. - Final releases register the schema fixture: add the tag/version to
backend/internal/schemafixture/releases.go, rungo run ./cmd/genschema, and commit the newbackend/database/testdata/schemas/<tag>.sql. An RC ships the final's schema and is exempt until promotion. - Discharge the ASVS/MASVS §10 obligation: the verification report needs a row
since the previous release tag, or a documented
ack_asvs_currentreason. Do this at milestone-gate close, not at dispatch. - Attest or explicitly skip every manual gate that applies
(
.github/manual-gates.json,attest_manual_gates). A skip needs a reason; it is not a pass. - Ensure
CHANGELOG.mdhas the section for this release (rename[Unreleased]to[X.Y.Z] - YYYY-MM-DDand start a new[Unreleased]);release.ymlrefuses to tag without it. - Run the release gates from the runbook and record failures as failures.
DoD
cd backend && go run ./cmd/releasegatecheck
cd backend && go run ./cmd/manualgatecheck validate -ledger ../.github/manual-gates.json -root ..
cd backend && go run ./cmd/asvsstale
cd backend && go run ./cmd/genschema
Report any check you could not run; never imply it passed. A release gate that could not be run is not green.
Stop and ask
- A required gate is red, flaky, or silently skipped on the release commit.
- The schema dump is missing, dirty, or not frozen (
genschemarewrites only the expected new dump). - The ASVS/MASVS report has no new §10 row and no acknowledged reason.
- A manual gate applies but has no fresh attestation and no recorded skip.
- The operator notes are missing a migration, config, or breaking change.
Canonical detail: docs/development/release-gates.md,
docs/security/release-verification.md, docs/changelog-policy.md.
04 同仓库更多 Skills
valid
Use when exercising a well-formed skill fixture in the agent-context tests.
unregistered-dod
Use when a fixture must carry a DoD command no Suite registers.
orphan-reference
Use when a fixture must exercise an unlinked reference file.
missing-reference
Use when a fixture must link to a reference file that does not exist.
missing-description
暂无简介
long-reference
Use when a fixture must exceed the reference line maximum.