Release
Cut an Inspector v2 release, two PRs and then a GitHub Release.
Install
npx skills add modelcontextprotocol/inspector --skill release -g -a claude-code -y- Repository
- modelcontextprotocol/inspector11.2k
- Category
- Git and review
- Updated
- 6d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Cut an Inspector v2 release, two PRs and then a GitHub Release. PR 1 puts the npm audit, any fixes it forces, and the version bump on v2/main; PR 2 merges v2/main into main and is smoke-tested from the production build with a ledger artifact for the maintainers; the maintainer then drafts the Release with a script and publishes it. Also covers the v1 line and what the publish jobs gate on.
Cutting a release
Background on what ships and why (the files allowlist, the bundling rules, the
container image) is in docs/publishing.md. This
skill is the procedure.
A v2 release is cut from main, after the milestone's work has been merged
there from v2/main, not from v2/main itself. The v1 line releases
independently from v1/main to the v1-latest tag and never touches main.
Publishing is automated by release-gated jobs in
.github/workflows/main.yml (github.event_name == 'release'), all downstream
of needs: [build, coverage], so a release cannot publish with either the build
job or the coverage gate red:
package, asserts the release tag matches the rootpackage.jsonversion, installs, runsnpm run pack:verifyas the pre-publish gate, thennpm packs the tarball and uploads it as an artifact. It holds noid-token.publish,needs: [package]; holdsid-token: writeand only downloads that tarball and runsnpm publish <tgz> --access public --provenance. No checkout, no dependency install, no build, the split keeps install scripts away from the OIDC publish token (#2483).publish-github-container-registry, the GHCR image.
The shape: two PRs, then the Release
There is one version number (only the root package.json has one, the
clients carry none), and the release moves through two pull requests in
order. They are not interchangeable and neither one's content belongs on the
other.
