Phase One Release Checklist
-
Branch Hygiene
- Ensure
mainis green (CI pipeline complete). - Review outstanding ADRs and docs for freshness.
- Ensure
-
Build & Test
just cijust build-releasejust api-export
-
Artefact Verification
- Binary:
target/release/revaer-app - Checksum:
sha256sum target/release/revaer-app - OpenAPI:
docs/api/openapi.json - Helm chart:
dist/helm/revaer-<version>.tgz - Helm provenance:
dist/helm/revaer-<version>.tgz.prov - Helm public key:
dist/helm/revaer-helm-public.asc - Helm public keyring:
dist/helm/revaer-helm-public.gpg - Docker image:
just docker-build && just docker-scan - Published GHCR image: verify Trivy scan, SBOM/provenance attestations, and Cosign signatures from the image workflow
- Published OCI chart: verify
oci://ghcr.io/<owner>/charts/revaer:<version>plus theartifacthub.iometadata tag andhelm verifyagainst the published public key
- Binary:
-
Runbook Execution
- Run
just runbook - Follow the remaining manual-only drills in
docs/runbook.md - Archive CLI telemetry,
/metrics,/health/fullsnapshots.
- Run
-
Documentation Refresh
- Verify ADRs 005–007 reflect current design.
- Update user guides (
docs/api/guides/*.md) with any behavioural changes.
-
Tag & Publish
- Create annotated tag:
git tag -a vX.Y.Z -m "Phase One release" - Push tag:
git push origin vX.Y.Z - Attach artefacts generated by the
build-releaseworkflow, including the Helm chart archive, provenance file, and Helm public key. - Confirm the OCI chart publish completed after the GitHub release so the
artifacthub.io/signKeyURL resolves. - Confirm the GHCR chart package is public so Artifact Hub can pull
oci://ghcr.io/<owner>/charts/revaeranonymously. - In Artifact Hub, add or claim
oci://ghcr.io/<owner>/charts/revaer, then verify that the publishedartifacthub.iometadata tag includes the expected repository ID and owner identity. - After Artifact Hub shows
Verified publisher, file theofficialstatus request for the Revaer publisher or organization. Userevaer-logo.pngfor the Artifact Hub repository and organization logo during that setup.
- Create annotated tag:
-
Post-Release Monitoring
- Watch rate-limit and guard-rail metrics.
- Confirm
HealthChangedevents return to empty degraded set. - Validate automation telemetry for CLI success rates.