Voyager Release

Use repository scripts and .github/workflows/release.yml as the source of truth. Normal releases use CI: a release tag builds the browser artifacts, signs and notarizes Safari, creates the GitHub Release, and submits the stores.

Choose the requested workflow

Read only the reference needed for the current task:

• New release, version bump, or interrupted release preparation: normal-release.md.
• Failed Chrome or Edge submission, or an urgent Firefox-only hotfix: store-recovery.md.
• Safari CI failure or an explicitly requested local recovery artifact: safari-dmg.md.
• Store listing copy about the plugin catalog connection (Chrome, Edge, Firefox): store-listing-plugin-catalog.md.

Authorization and publication boundaries

The user's request and existing approval define the scope; loading this skill grants no additional permission. Complete authorized preparation and verification, and reuse approval for the same version, destination, and action. A diagnosis or preparation request does not by itself authorize publication.

Before a tag push, store submission, or replacement upload, verify that the concrete action is authorized. Ask only when that authorization is missing or the version, scope, or a possible release blocker needs a user decision; prepare the reviewable result first. Explain any newly discovered change to the approved release.