Repository navigation
Tag and publish the release when a version bump reaches main - #5
Merged
Merged
Conversation
.github/workflows/release.yml runs when .claude-plugin/marketplace.json changes on main. It fails if CITATION.cff has a different version, does nothing if the tag already exists, and otherwise tags the commit with an annotated vX.Y.Z and publishes the GitHub release with the merged pull request's description as its notes. CONTRIBUTING.md explains the steps.
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.
Releases 1.0.0 to 1.2.0 were tagged and published by hand, so a merged version bump did not show up as a release until someone did it. This adds a workflow that does it on merge.
It runs when
.claude-plugin/marketplace.jsonchanges onmain, and can also be started by hand. It reads the version and stops with an error ifCITATION.cffhas a different one. If the tag already exists it does nothing, so running it again is safe. Otherwise it tags the merge commit with an annotatedvX.Y.Zand publishes the release, with the merged pull request's description as the notes. When it finds no pull request it falls back to GitHub's generated notes.This pull request does not change the version, so merging it publishes nothing.
actionlintpasses, and I checked the version read and the pull request lookup locally against the 1.2.0 merge commit. The workflow itself has not run yet; the next version bump will be its first run.CONTRIBUTING.mdhas a new Releases section, run throughcheck.sh.