Repository navigation
Release process: RELEASING.md, pre-releases under next, 0.1.1-beta.0 - #1
Merged
Merged
Conversation
A pre-release must never become `latest`, and npm 11 refuses to publish one without an explicit --tag. The workflow now passes the GitHub Release's prerelease flag to check-release, which refuses the release before any build when the flag and the version suffix disagree, and npm publish takes --tag next or latest from that same flag. The flag is required as true or false: a missing value would otherwise read as stable and let the first mistake through.
First version published by the workflow, as a pre-release under the next dist-tag, to validate Trusted Publishing before its deadline without moving latest.
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.
What
publish.ymlwith npm Trusted Publishing and provenance), the one-time setup and its status, pre-releases, and troubleshooting. The Publishing section of CONTRIBUTING.md now points to it.x.y.z-beta.N) on a Release marked "Set as a pre-release" publishes under thenextdist-tag, neverlatest.scripts/check-release.mjsrefuses the release before any build when the suffix and the flag disagree.Why now
The trusted publisher on npmjs.com is configured but pending validation: npm needs one publish from this workflow before 2026-10-21 23:20 UTC. Releasing
v0.1.1-beta.0as a pre-release validates it without touchinglatest(0.1.0).Verified
npm run typecheckclean;npm test150/150 pass;npm run verify:packok (26 files).check-releaseby hand: beta + pre-release ok, beta + not pre-release refused, stable + pre-release refused, stable ok, build metadata (+build) not treated as a pre-release, missing/invalid flag refused.After merging
Publish a GitHub Release from
main: tagv0.1.1-beta.0, titlev0.1.1-beta.0, notes from the CHANGELOG, "Set as a pre-release" checked. Thennpm view @the-coded/llm-adapters dist-tagsshould shownext: 0.1.1-beta.0andlatest: 0.1.0.