⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Jan 23, 2026

Automated Release PR

4.3.0 (2026-02-11)

Full Changelog: v4.2.4...v4.3.0

⚠ BREAKING CHANGES

  • mcp: remove deprecated tool schemes
  • mcp: 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.

Chores

  • mcp: remove deprecated tool schemes (8969ed3)
  • remove custom MCP server code, align with Stainless generated output (74db9f7)

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

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
@batuhan batuhan changed the title release: 5.0.0 release: 4.3.0 Jan 28, 2026
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Jan 28, 2026

Release version edited manually

The Pull Request version has been manually set to 4.3.0 and will be used for the release.

If you instead want to use the version number 5.0.0 generated from conventional commits, just remove the label autorelease: custom version from this Pull Request.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--desktop-api branch from 771c555 to 4745bc7 Compare January 28, 2026 20:29
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Feb 11, 2026

🧪 Testing

To try out this version of the SDK, run:

npm install 'https://pkg.stainless.com/s/beeper-desktop-api-typescript/74db9f7f9a1a59ce6c36c1ab5b6a2d71767f4ff7/dist.tar.gz'

Expires at: Fri, 13 Mar 2026 18:05:22 GMT
Updated at: Wed, 11 Feb 2026 18:05:22 GMT

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--desktop-api branch from 4745bc7 to 9dd64d5 Compare February 11, 2026 18:07
@batuhan batuhan merged commit ec4285a into main Feb 11, 2026
7 checks passed
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Feb 11, 2026

🤖 Release is at https://github.com/beeper/desktop-api-js/releases/tag/v4.3.0 🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant