Skip to content

rollout-checklist.md

Latest commit

 

History

History
67 lines (54 loc) · 3.14 KB

rollout-checklist.md

File metadata and controls

67 lines (54 loc) · 3.14 KB

v0.26.2 Rollout Checklist

Step-by-step playbook for the v0.26.2 release. Each phase must complete before advancing.

Phase 0: Pre-flight

  • Verify all release package versions are 0.26.2:
    • apps/server/package.json
    • apps/desktop/package.json
    • apps/web/package.json
    • apps/mobile/package.json
    • packages/contracts/package.json
  • Verify Android versionName and iOS MARKETING_VERSION both match 0.26.2.
  • Confirm CHANGELOG.md has ## [0.26.2] - 2026-04-21.
  • Confirm docs/releases/v0.26.2.md exists with Summary, Highlights, Upgrade and install, and Release operations sections.
  • Confirm docs/releases/v0.26.2/assets.md exists and lists every expected attachment class.
  • Confirm docs/releases/v0.26.2/rollout-checklist.md and docs/releases/v0.26.2/soak-test-plan.md exist.
  • Confirm docs/releases/README.md includes the v0.26.2 row.
  • Run bun run release:validate 0.26.2.
  • Confirm the working tree is clean.
  • Confirm you are on main.

Quality gates

  • bun run fmt:check
  • bun run lint
  • bun run typecheck
  • bun run test
  • bun run --cwd apps/web test:browser
  • bun run test:desktop-smoke
  • bun run release:smoke

Phase 1: Publish

  • Push the release-prep commit to main.
  • Create and push tag v0.26.2.
  • Verify the coordinated release.yml workflow starts.
  • Trigger release-ios.yml manually for v0.26.2 (or the matching release ref if the tag is unavailable).
  • Monitor release.yml through Preflight, Desktop builds, Publish CLI, Publish GitHub Release, and Finalize release.
  • Monitor release-ios.yml through Preflight, iOS signing preflight, and iOS TestFlight.

Asset verification

  • GitHub Release body matches docs/releases/v0.26.2.md.
  • okcode-CHANGELOG.md is attached.
  • okcode-RELEASE-NOTES.md is attached.
  • okcode-ASSETS-MANIFEST.md is attached.
  • macOS release artifacts are attached: DMG, ZIP, updater manifest, and blockmaps.
  • Linux release artifacts are attached: AppImage and updater manifest if generated.
  • Windows release artifacts are attached: installer, updater manifest, and blockmaps.
  • If the Intel compatibility workflow is run, confirm the x64 macOS DMG is attached separately.

Phase 2: Post-release verification

  • npm exec --yes --package okcodes@0.26.2 -- okcode --version returns 0.26.2.
  • macOS installer launches and passes Gatekeeper.
  • Linux AppImage launches.
  • Windows installer installs and launches.
  • Desktop auto-update metadata is present for supported platforms.
  • If iOS signing was enabled, confirm the new TestFlight build appears.
  • Confirm the finalize job did not need to push another version-alignment commit, or review its no-op output if versions were already aligned before tagging.

Phase 3: Follow-through

  • Trigger the Intel compatibility workflow if macOS x64 artifacts are required for this train.
  • Update external release references or announcements.
  • Monitor reports for regressions in provider onboarding, auth flows, release packaging, and cross-platform install/update behavior.