Release-store Workflow

This page documents .github/workflows/release-store.yml, the publish workflow used for tagged releases.

Purpose

It takes release-ready build output and publishes it to the public delivery targets.

Triggers

• push tags matching v*
• manual workflow_dispatch

Main stages

1. Check out repository source.
2. Restore build caches.
3. Build protocol v2 dist/.
4. Build legacy v1 zip output.
5. Create release bundles.
6. Upload release artifacts and reports.
7. Save build caches.
8. Write a release summary.
9. Deploy dist/ to gh-pages.
10. Refresh CDN cache endpoints.
11. Create a GitHub Release with attached bundles.

Publish outputs

The workflow currently publishes or attaches:

• gh-pages static dist/ output for the v2 protocol
• main.zip for legacy v1 compatibility
• zipped release bundles for download
• JSON build reports for troubleshooting

Why it matters

This workflow is the closest reference if you want a third-party store repository to match the official publish path.

It shows how the official repository separates:

• build-time artifacts
• publish-time deployment
• release attachments for manual download

Related build workflow

The non-publishing build workflow is documented in Release Workflow.

If you are designing an external repository, see Official Actions Reuse for the recommended reuse path.