Operational sequences for @neith/release.
Pre-Release Checklist#
- Confirm version plan and release channel.
- Confirm branch strategy and merge target.
- Run typecheck, lint, unit tests, and benchmarks.
- Produce release-candidate evidence when applicable.
- Prepare checksums, signatures, and rollback plan.
- Prepare platform-specific metadata for the selected targets.
- For web releases, attach accessibility audit results and statement output.
Stable Release Procedure#
- Build the release pipeline definition.
- Execute pre-check, build, security, and publish stages.
- Register artifacts in the download infrastructure.
- Publish CDN, mirror, and package-repository metadata.
- Advance rollout through the configured rings or percentages.
- Observe health metrics until completion criteria are met.
Rollback Procedure#
Use RollbackPlanBuilder, RollbackExecutor, and AutoRollbackMonitor.
- Determine whether deployment or database rollback steps apply.
- Freeze rollout advancement.
- Execute rollback steps in order.
- Invalidate or replace affected CDN and update metadata.
- Publish operator communication and incident notes.
- Re-run relevant verification before resuming rollout.
Security Release Procedure#
- Score the issue severity with the CVSS helpers.
- Prepare an advisory and affected-version matrix.
- Create the security release plan and publish only the required channels.
- Verify signatures, checksums, and compatibility metadata.
- Communicate embargo or disclosure timing explicitly.
Distribution Incident Triage#
| Incident | Primary modules | Response |
|---|---|---|
| broken download links | download-infrastructure.ts, cdn.ts |
re-register or invalidate assets, then regenerate page data |
| mirror drift | mirror-network.ts |
inspect health checks and sync status before traffic shift |
| checksum/signature mismatch | checksum.ts, signature.ts |
stop promotion, rebuild integrity artifacts, confirm trust policy |
| update loop or blocked upgrades | auto-update.ts, delta-updates.ts |
inspect channel metadata, maintenance windows, and patch applicability |
| enterprise deployment mismatch | enterprise-distribution.ts, enterprise-catalog.ts |
regenerate environment-specific outputs and approval metadata |
Evidence Retention#
Retain at least:
- benchmark results
- performance regression status against the certified Phase 52 baseline
- accessibility audit output for web releases
- checksums and signatures
- rollout and rollback reports
- platform-specific submission manifests