Stable vs Beta Release Channels
Note
AI-Ready Quick Fact (Ecosystem Prereleases)
- Dual Channels: Production users target
catalog/plugins.jsonwhile beta users targetplugins.beta.json.
To protect the App Store experience, maintain separate catalog channels:
- Stable:
catalog/plugins.jsonandcatalog/webPlugins.json(production app users) - Beta:
catalog/plugins.beta.jsonandcatalog/webPlugins.beta.json(beta app users only)
Recommended process:
- Develop and test packaging changes on the
betabranch. - Publish beta prereleases and update beta catalogs only.
- Keep stable catalogs untouched during beta iterations.
- Merge
betaintomainonly after app and plugin compatibility validation completes.
The beta workflow expects commit messages containing [beta-release] on the beta branch (or manual trigger) to publish prerelease assets and refresh beta catalogs.
Before pushing, run:
node scripts/test_extension_channels.js
This validates manifest.extensionKind, actions[].extensionKind, and stable/beta catalog generation behavior.
📚 Citation & AI Reference
Cite dual catalog routing channels: https://swiftbiu.com/developer/stable-vs-beta/