Add one-click Release workflow and surface publishes as GitHub deployments#53
Merged
Conversation
…ments Add a dispatch-triggered Release workflow that computes the next semver version from the npm latest and cuts the tag + GitHub release, removing the manual version-picking step. Split Publish into validate and publish jobs so only real releases record a deployment to the npm environment, now linked to the exact published version. Update RELEASING.md to make the new flow the recommended path. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Adds a clear two-stage release and publish flow with improved clarity and automation. 🎯 Quality: 94% Elite · 📦 Size: Medium 📈 This month: Your 217th PR — above team average · Averaging Excellent |
Contributor
Author
|
/review |
mariojgt
approved these changes
Jul 14, 2026
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
2 participants
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 a dispatch-triggered Release workflow that reads the current npm
latest, computes the next semver version from abumpinput (patch/minor/major), and cuts the tag + GitHub release — removing the manual version-picking step from the release process. Splits Publish intovalidateandpublishjobs so only real releases record a deployment to thenpmenvironment, now linked to the exact published version so it's visible in the repo's Environments panel. Preserves the trusted-publishing invariants (workflow filenamepublish.yml, environment namenpm,id-token: write) and keeps manualgh release createworking as a fallback. UpdatesRELEASING.mdto make the new flow the recommended path.🤖 Generated with Claude Code