chore: bump version to 0.5.0 - #58
Merged
Merged
Conversation
The rename to @pcmstack/mcp changes the package and bin names, which breaks existing configs, so this goes in the minor slot rather than a patch. Bumps the bundle manifest alongside package.json, as the .mcpb carries its own version. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Bumps the project version to 0.5.0 to prepare the first release under the @pcmstack/mcp package name, keeping the npm package and bundled .mcpb manifest in sync.
Changes:
- Updated
package.jsonversion from0.4.1to0.5.0. - Updated
package-lock.jsonroot/package versions to0.5.0. - Updated
manifest.jsonversion to0.5.0to match the npm release.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Bumps the published package version to 0.5.0. |
| package-lock.json | Aligns lockfile package version metadata to 0.5.0. |
| manifest.json | Aligns .mcpb manifest-reported version to 0.5.0. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
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
Bumps the version to 0.5.0 for the first release under the
@pcmstack/mcpname.The minor slot rather than a patch: the package rename and the new
pcmstackbin entry both break existing setups, and pre-1.0 that is where breaking changes belong. Staying on 1.0.0 is left for an explicit stability decision, not a side effect of the rename.manifest.jsonis bumped alongsidepackage.json, since the.mcpbbundle carries its own version and would otherwise advertise 0.4.1 to Claude Desktop while npm serves 0.5.0.Before tagging the release
The publish workflow will fail unless, on npmjs.com:
pcmstackorganization exists and this account can publish to it@pcmstack/mcpis registered as a trusted publisher for this repository's workflow (the release job authenticates through OIDC)Note that the new package starts with no history: the versions published as
pcm-mcpdo not carry over. After the release,pcm-mcpshould be deprecated pointing at the new name.Test plan
npm test— 180 tests passingpackage.json,package-lock.jsonandmanifest.json🤖 Generated with Claude Code