chore: set up release/0.1 as the 0.1 maintenance branch - #55
Merged
Merged
Conversation
release/0.1 was cut from v0.1.0-alpha.23 so 0.1 consumers can get fixes after main moved to 0.2. A release runs the publish workflow from the tagged commit, so this branch needs its own dist-tag rule: the old one sent any -alpha version to `alpha`. Port scripts/dist-tag.mjs from main and use it in both publish jobs: a 0.1 version publishes under release-0.1 and never moves next, latest or alpha. CI also runs on pushes to release/**. README, CONTRIBUTING and CHANGELOG say this is the maintenance branch and how a 0.1 patch is released.
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The documented release command contains shell redirection syntax and cannot run as written.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
Establishes release/0.1 as the maintained 0.1 release branch.
Changes:
- Adds release-line-aware npm dist-tag selection and tests.
- Updates publishing and CI workflows for maintenance branches.
- Documents 0.1 installation and release procedures.
| File | Description |
|---|---|
scripts/dist-tag.mjs |
Selects dist-tags by release line. |
scripts/dist-tag.d.mts |
Declares script exports for TypeScript. |
src/distTag.test.ts |
Tests release-line and tag selection. |
.github/workflows/publish.yml |
Uses the dist-tag script for publishing. |
.github/workflows/ci.yml |
Runs CI on release branches. |
README.md |
Documents 0.1 maintenance and installation. |
CONTRIBUTING.md |
Adds the 0.1 release procedure. |
CHANGELOG.md |
Records the maintenance-branch policy. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Address ready-gate review: a separate dist-tag job reads main once and both publish jobs take its outputs, so the two registries cannot disagree if main moves to a new line between them. The documented gh release command no longer uses a <placeholder> the shell reads as redirection.
Member
Author
Ready-gate agent review (Opus) — blocking issues onlyNO BLOCKING ISSUES (reviewed at Copilot: reviewed — its findings were fixed in |
yomybaby
marked this pull request as ready for review
October 2, 2026 06:26
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
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.
Summary
release/0.1is cut fromv0.1.0-alpha.23to carry 0.1 hotfixes and patch releases now thatmainis 0.2. A GitHub release runs the publish workflow from the tagged commit, so this branch needs its own dist-tag rule — the 0.1 workflow sends any-alphaversion toalpha.scripts/dist-tag.mjs+src/distTag.test.ts, ported verbatim from main's PR chore: maintain 0.1 on release/0.1 and publish its patches under release-0.1 #56: a 0.1 version publishes underrelease-0.1only;next,latestandalphado not move.publish.yml: both jobs use it.ci.yml: also runs on pushes torelease/**.@release-0.1.0.1.0-alpha.Nversioning,gh release create --target release/0.1 --prerelease --latest=false, dist-tag check).Verification
pnpm run verifyon this branch — passes (591 tests, including the 5 new ones; pack check clean, the test is not shipped).