Repository navigation
Release 0.4.1: plugin.json holds the only version - #53
Conversation
The marketplace now follows main, so a plugin.json version bump releases; a workflow tags vX.Y.Z on merge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e0b62bfcc0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| git tag "$tag" | ||
| git push origin "$tag" |
There was a problem hiding this comment.
On any main push touching the manifest, this step publishes the version tag immediately. The repository's tests and lint checks are separate push-triggered workflows in .github/workflows/test.yaml and .github/workflows/lint.yaml, so a failing check cannot block this release; GitHub Actions allows separate workflow runs to execute concurrently by default. Consequently, a bad version bump can create the immutable tag consumed by pinned analysis repositories before CI reports the failure. Run the required checks as prerequisite jobs or trigger tagging only after their successful completion.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Moot now: the tag workflow is gone (see the PR description). Releases are a plugin.json bump, and nothing tags automatically.
…ed versions in docs Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Marius1311
changed the title
1 participant
The marketplace now follows each plugin's
main(quadbio/claude-plugins#11), as Claude Code's docs recommend for a plugin with aversion: bump it and push, and users update when it changes. So a release is one line in.claude-plugin/plugin.json; the README's Release section says so.pyproject.tomlreads its version fromplugin.json, so the test that kept the two in sync is gone.Releases 0.4.1: everything merged since the last release.
🤖 Generated with Claude Code