Skip to content

Follow each plugin's main; releases are version bumps #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Marius1311 merged 1 commit into from
Oct 13, 2026
Merged

Follow each plugin's main; releases are version bumps #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions .claude-plugin/marketplace.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,7 @@
"description": "Conventions, guard hooks and a small package for analysis repos where humans (notebooks) and coding agents (scripts) work side by side.",
"source": {
"source": "url",
"url": "https://github.com/quadbio/analysis-workflow.git",
"ref": "v0.2.1"
"url": "https://github.com/quadbio/analysis-workflow.git"

@chatgpt-codex-connector chatgpt-codex-connector Bot Oct 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep remote sources pinned to released refs

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 👍 / 👎.

@Marius1311 Marius1311 Oct 13, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

}
},
{
Expand All @@ -29,17 +28,15 @@
"description": "Run coding agents on ETH Zurich's Euler cluster: node, allocation, storage rules and your setup at session start; a skill for Slurm jobs, software and data; jobs listed by session.",
"source": {
"source": "url",
"url": "https://github.com/quadbio/euler-hpc.git",
"ref": "v0.2.1"
"url": "https://github.com/quadbio/euler-hpc.git"
}
},
{
"name": "sci-figures",
"description": "Nature-style research figures and their legends: outline, layout and visual conventions, export to editable PDFs, legend writing and independent reviews.",
"source": {
"source": "url",
"url": "https://github.com/quadbio/sci-figures.git",
"ref": "v0.2.0"
"url": "https://github.com/quadbio/sci-figures.git"
}
}
]
Expand Down
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,5 +20,5 @@ Then turn on updates, which are off by default for marketplaces outside Anthropi
Marketplaces → quadbio → Enable auto-update ([docs](https://code.claude.com/docs/en/plugins/install#keep-plugins-updated)).

Each plugin lives in its own repository; this one only lists them. A plugin's README opens with what it does
and its parts, then `Use`, `Install` (pointing here), `Develop`, `Release`. To release a pinned plugin, bump its
`ref` here.
and its parts, then `Use`, `Install` (pointing here), `Develop`, `Release`. Entries follow each plugin's `main`: a
plugin releases by bumping `version` in its `plugin.json`.