Release Manager Quickstart

A guided checklist for engineers coordinating extension and wallet-core releases.

1. Pre-release checks

Before cutting a release, ensure the main branch is green and that you can run the full pipeline locally:

• bun run lint
• bun run build (once)
• bun run check:bundle
• bun tests/validation/validate-manifest.js
• bun run test:unit
• bun run test:integration
• bun run test:e2e
• bun run security (or bun run security:all for a full pass)
• bun audit

2. Security & ADR review

• Review SECURITY.md and ensure the documented policy still matches implemented behaviour and current practices.
• Visit Architecture Decisions and skim recent ADRs for any changes that impact the release.
• Confirm that security-relevant changes (keys, storage, capability model, RPC surfaces) are covered by tests and documented ADRs.

3. Packaging and distribution

• Build the extension bundle and verify dist/manifest.json matches MV3 constraints.
• Load the unpacked bundle in a fresh browser profile and perform a smoke test (unlock, connect dApp, send a transaction).
• For @keetanetwork/wallet-core, ensure Typedoc generation and publishing pipelines complete successfully.

4. Security fixes and advisories

• When a release includes security fixes, follow the incident response and disclosure guidance inSECURITY.md.
• Prepare short release notes or advisories that describe the impact, affected components, and recommended upgrade paths.

5. Post-release

• Monitor error reporting, logs, and user feedback channels for regressions.
• Capture any follow-up work (for example, additional ADRs or docs updates) in issues and schedule them for the next cycle.