Repository navigation
Follow each plugin's main; releases are version bumps - #11
Conversation
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: 1acf8d26a1
ℹ️ 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".
| "source": "url", | ||
| "url": "https://github.com/quadbio/analysis-workflow.git", | ||
| "ref": "v0.2.1" | ||
| "url": "https://github.com/quadbio/analysis-workflow.git" |
There was a problem hiding this comment.
When any of these repositories merges development work between version bumps, a fresh installation now checks out the default branch's current HEAD because an omitted ref defaults to that branch (marketplace reference); the manifest version only prevents existing users from replacing their cached copy until that string changes (release guidance). Consequently, new and existing installations can run different code while reporting the same released version, so a version bump does not actually define the release boundary. Keep these entries on release tags, or use a stable branch advanced only alongside the version bump; the same issue applies to the newly unpinned euler-hpc and sci-figures entries.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Declining: this is the flow Claude Code's docs recommend for a plugin that sets version (Publish a plugin → Release a new version: "increment it and push"; tags only for dependency ranges). A fresh install between bumps gets reviewed main under the previous number, and existing users move at the next bump. We tried a release branch moved by CI and dropped it: more machinery than the gap is worth for a lab-internal marketplace.
1 participant
Drops the three
refpins, so every entry follows its plugin'smain, as cell-type-annotation already did. Claude Code updates a plugin when itsplugin.jsonversion changes, so a release is one version bump in the plugin's repo, the flow its docs recommend (quadbio/analysis-workflow#9, quadbio/sci-figures#2, quadbio/cell-type-annotation#53, quadbio/euler-hpc#2). This repo changes only when a plugin is added, renamed or removed.Merge the four release PRs first; until then new installs get merged but unreleased changes under the old version numbers.
🤖 Generated with Claude Code