Repository navigation
ci: cut a GitHub Release when the package publishes - #7
Merged
Merged
Conversation
The last two releases here were cut by hand and then stopped, so 1.0.3 shipped to npm and the registry with no release to show for it. The tag now follows package.json like the two registries do — a fourth place the version could disagree, closed. Idempotent: an existing release is reported and skipped. The registry job keeps contents: read; only the npm job needs write. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V5hFP2B2vU4dUMYgM1NEVs
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
1 participant
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.
The last two releases here were cut by hand and then stopped, so
1.0.3shipped to npm and the MCP registry today with no release to show for it.The tag now follows
package.jsonexactly like the two registries do — a fourth place the version could disagree, closed. Cut in the npm job right after the publish succeeds, and only when it published.Idempotent: an existing release is reported on the job summary and skipped rather than failing the run. Only the npm job moves to
contents: write; the registry job stayscontents: readsince it creates nothing.1.0.3is already on both registries, so I'll cutv1.0.3by hand once this lands and everything after is automatic.🤖 Generated with Claude Code
https://claude.ai/code/session_01V5hFP2B2vU4dUMYgM1NEVs