release: 0.30.0 #79
Open
release: 0.30.0 #79
Conversation
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
Contributor
Author
|
🧪 Testing To try out this version of the SDK, run: Expires at: Sun, 08 Feb 2026 05:51:47 GMT |
This removes all tool schemes except for "code mode" tools. Specifically, this removes "all tools" and "dynamic tools" schemes. Additionally, this removes support for resource filtering, tags, jq filtering, and compatibility controls in MCP servers, as they are no longer necessary when using code mode. # Migration To migrate, simply modify the command used to invoke the MCP server. Currently, the only supported tool scheme is code mode. Now, starting the server with just `node /path/to/mcp/server` or `npx package-name` will invoke code tools: changing your command to one of these is likely all you will need to do. Specifically, you must remove all flags including things like --resources, --tags, --client, --tools=dynamic, etc from your invocation command. The only supported flags are now `--port`, `--transport`, `--socket`, and `--tools=docs` (specifically for "docs"). These are also the only options available for http servers. migration-effort: small
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
2515bf9 to
2f618fc
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
2f618fc to
a56895a
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
a56895a to
1d92a24
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
1d92a24 to
6edf781
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
6edf781 to
4759957
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
4759957 to
ebab08e
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
ebab08e to
3948d39
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
3948d39 to
3f1106b
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
3f1106b to
e20fdc0
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next--components--hyperspell
branch
from
e20fdc0 to
a003407
Compare
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.
Automated Release PR
0.30.0 (2026-01-09)
Full Changelog: v0.29.0...v0.30.0
⚠ BREAKING CHANGES
node /path/to/mcp/serverornpx package-namewill invoke code tools: changing your command to one of these is likely all you will need to do.Bug Fixes
Chores
Documentation
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions