Repository navigation
feat(release): add dist-tag, make-latest and prerelease support - #243
Merged
Merged
Conversation
Allow releasing older majors from maintenance branches without moving the npm `latest` dist-tag or the GitHub latest release. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 15, 2026
Accept prepatch, preminor, premajor and prerelease, with an optional preid input. Prereleases are flagged as such on GitHub, never marked as latest, and are refused under the 'latest' dist-tag.
mcollina
changed the title
There was a problem hiding this comment.
🟢 Approval recommended
The workflow and documentation changes are consistent, with no unresolved findings or blocking issues identified.
0 open findings
What changed in this PR
Extends the reusable release workflow to support maintenance releases and prereleases while preserving existing defaults.
Changes:
- Adds
dist-tag,make-latest, andpreidinputs. - Supports prerelease version bumps and prevents prereleases from being published as latest.
- Documents maintenance-branch and prerelease usage.
| File | Description |
|---|---|
| README.md | Documents new inputs and release examples. |
| .github/workflows/reusable-release.yml | Adds release controls, prerelease validation, and GitHub release flags. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Tony133
previously approved these changes
Oct 16, 2026
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Eomm
previously approved these changes
Oct 16, 2026
Tony133
reviewed
Oct 16, 2026
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
mcollina
added a commit
to fastify/fast-uri
that referenced
this pull request
Oct 17, 2026
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
mcollina
added a commit
to fastify/fast-uri
that referenced
this pull request
Oct 17, 2026
Pin the reusable release workflow to the fastify/workflows#243 merge and allow the pre* bump types (published under `three-next`), as on v2.x. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Adds optional inputs to
reusable-release.yml:dist-tag(defaultlatest): passed tonpm publish --tag.make-latest(defaulttrue): forwarded to the GitHub release'smake_latest.preid(default empty): prerelease identifier passed tonpm version --preid.semvernow also acceptsprepatch,preminor,premajorandprerelease. Prereleases are flagged as such on the GitHub release, never marked as latest, and are refused under thelatestdist-tag.Defaults keep current behavior. This makes the workflow usable from maintenance branches (e.g. fast-uri
v2.x/v3.x, published under thetwo/threedist-tags): without it,npm publishwould try to applylatestto an older version (rejected by npm 11, or movinglatestbackwards on older npm) and the GitHub release would be marked as latest.🤖 Generated with Claude Code