Repository navigation
ci(release): add release-please and plugin CI workflows - #2
Merged
Merged
Conversation
Release-please keeps a release PR on main and bumps each mod's plugin.json version, tagging vX.Y.Z like the web project. The Main workflow validates the marketplace and every mod and runs their tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Summary
Sets up releases and CI the same way the web project does.
release-please-config.jsonand.release-please-manifest.json: the same settings as web (include-component-in-tag: false,always-bump-patch, the same changelog sections), starting from0.1.0. The release type issimplebecause the repo has nopackage.json.extra-filesalso updatesversioninplugins/shelltime-statusline/.claude-plugin/plugin.json, which is how Claude Code knows installed copies need updating..github/workflows/release.yml: runs release-please on every push tomain. The marketplace is served from the repo, so merging the release PR is the release: it tagsvX.Y.Z, updatesCHANGELOG.mdand bumpsplugin.json..github/workflows/main.yml: runs on PRs and pushes tomain. It installs Claude Code, runsclaude plugin validate --stricton the marketplace and every folder underplugins/, and runsclaude plugin teston each one.README.md: a short Release section, including a reminder to add each new mod'splugin.jsontoextra-files.Test plan
HOME. Validation passes and all 25 tests pass, with no auth and no generated types.chore(main): release 0.1.1, touching onlyCHANGELOG.md,.release-please-manifest.jsonandplugin.json, with noversion.txt.🤖 Generated with Claude Code