Repository navigation
ci: auto-publish to npm and GitHub release on version bump - #17
Merged
Merged
Conversation
Publishes the package, tags vX.Y.Z and creates a GitHub release whenever the version in package.json on main is not yet on npm. Co-Authored-By: Claude Opus 5.5 <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.
Summary
Adds
.github/workflows/release.yml, which runs on pushes tomainthat changepackage.json(or manually via workflow_dispatch):versionfrompackage.json; if that version is not yet on npm, builds (yarn prepare) and publishes with provenance. Pre-release versions (x.y.z-beta.n) go to thenextdist-tag.vX.Y.Ztag and a GitHub release with auto-generated notes (reuses the tag if it already exists).Setup required before merge
NPM_TOKENrepo secret (npm automation token with publish rights), or configure npm Trusted Publishing for this repo/workflow.package.jsonis at2.0.1, which is not on npm yet (latest is2.0.0), so the next push tomainthat touchespackage.jsonwill publish 2.0.1.release-itscript also publishes/tags; use one flow or the other.🤖 Generated with Claude Code