chore(main): release jacobian 0.8.0 - #335
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 091bbcfdc3
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "source": "github" | ||
| }, | ||
| "version": "0.7.0", | ||
| "version": "0.7.1", |
There was a problem hiding this comment.
Publish the matching npm package version
For the 0.7.1 release, this line moves the MCP server metadata to 0.7.1 but the same server.json still declares packages[0].version as 0.7.0. The publish-mcp workflow checks out this immutable release commit and publishes this metadata, so MCP Registry installers will be told to run the old npm package even though the registry entry is 0.7.1, skipping the 5205fd9 fix for registry consumers. Update the package entry to 0.7.1 together with the top-level version.
Useful? React with 👍 / 👎.
f61d83d to
c91f7ee
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 34a4aa1b5b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "source": "github" | ||
| }, | ||
| "version": "0.7.0", | ||
| "version": "0.8.0", |
There was a problem hiding this comment.
Publish the 0.8.0 package in registry metadata
Fresh evidence: this 0.8.0 bump changes only the server metadata version while packages[0].version remains 0.7.0; the release workflow checks out this immutable release SHA and then runs ./mcp-publisher publish, and the MCP versioning guidance says local server/package versions should align (https://modelcontextprotocol.io/registry/versioning#align-server-version-with-package-version). For this release, MCP Registry consumers will still be given jacobian@0.7.0 even though the Python and npm packages are 0.8.0, so registry installs miss the new release’s fixes.
Useful? React with 👍 / 👎.
d32a9da to
a98092b
Compare
e0f19a2 to
c457497
Compare
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
0.8.0 (2026-08-03)
Features
Bug Fixes
Dependencies
Documentation
This PR was generated with Release Please. See documentation.