ci: publish prereleases from main on the alpha channel - #23
Merged
Conversation
Switch semantic-release so `main` publishes prereleases (X.Y.Z-alpha.N) to the
npm `alpha` dist-tag instead of stable releases to `latest`. The first stable
release will be 3.0.0 — the next major above the prematurely published,
now-deprecated 2.x.
- release.config.mjs: branches = ["stable", { name: "main", prerelease:
"alpha" }]. `stable` is an inert placeholder required by semantic-release
(it rejects a prerelease-only config); no release commits go to it until the
3.0.0 cutover.
- CLAUDE.md: document the alpha-by-default policy and the 3.0.0 cutover steps.
The 0.0.0 and 2.0.x versions are deprecated on npm separately (manual, requires
npm auth). `latest` stays on 2.0.3 until the 3.0.0 cutover.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
dogmar
force-pushed
the
claude/gallant-yalow-5766c1
branch
from
June 15, 2026 20:19
30de647 to
3b36d6f
Compare
✅ Deploy Preview for colander-cal canceled.
|
Contributor
|
🎉 This PR is included in version 3.0.1-alpha.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Switches the publish strategy so this pre-stable package stops shipping to the npm
latestchannel and instead publishes alpha prereleases by default, building up to a real first stable release of3.0.0.Changes
release.config.mjs—branches: ["release/stable", { name: "main", prerelease: "alpha" }].mainnow publishesX.Y.Z-alpha.Nto the npmalphadist-tag.release/stableis an inert placeholder branch: semantic-release rejects a prerelease-only config (ERELEASEBRANCHES), so a stable release branch must exist. It's folder-prefixed to satisfy the Enforce branch folders repo ruleset and is created atv2.0.3. No release commits go to it until the 3.0.0 cutover.CLAUDE.md(new) — durable marker documenting the alpha-by-default policy and the 3.0.0 cutover procedure for agents/contributors.Versioning
v2.0.3is at HEAD with no new commits, so no release fires from merging this PR (it's aci:commit). The first alpha publishes on the next version-bumping commit onmain.3.0.0-alpha.1(and ultimately3.0.0), that range must include a breaking change (feat!:/BREAKING CHANGE:). A plainfeat:would produce a2.xalpha line instead.Out of band (manual, needs npm auth)
0.0.0and2.0.0–2.0.3on npm. No unpublish;lateststays on the (deprecated)2.0.3until the 3.0.0 cutover.🤖 Generated with Claude Code