Repository navigation
Publish releases automatically when the version changes - #3
Merged
Merged
Conversation
Run npm test on every push to main and every pull request, on Node 18, 20 and 22 (Linux) plus Node 22 on Windows. Add a status badge to the README. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After the Test workflow passes on main, tag plugin.json's version and publish a GitHub Release with generated notes, unless that tag exists. Add `npm run bump -- X.Y.Z` to set the version in all three manifests, and a test that fails when they disagree. 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
Continuous delivery for the plugin: merging a version bump publishes a release.
.github/workflows/release.yml: runs after the Test workflow succeeds for a push tomain. Reads the version from.claude-plugin/plugin.json; ifvX.Y.Zis not tagged yet, creates the tag on the tested commit and publishes a GitHub Release with auto-generated notes. Otherwise it exits without doing anything.npm run bump -- X.Y.Z(scripts/bump-version.mjs): sets the version inpackage.json,plugin.jsonandmarketplace.json, editing only the version line so formatting is untouched.tests/version.test.mjs: fails CI if the three versions disagree, so a half-done bump cannot be merged.Notes
0.1.0has never been tagged, so the first passing run onmainafter merge will publish v0.1.0 for the current code.workflow_run.head_sha), andconcurrency: releaseprevents two runs racing on the same tag.Testing
npm test: 17 pass (new version test included).npm run bump -- 9.9.9changed one line in each manifest and tests still passed; reverting withbump -- 0.1.0left no diff; an invalid version is rejected.mainafter merge (workflow_runtriggers from the default branch only).🤖 Generated with Claude Code