Prepare v6.0.0 Desktop API and MCP release - #46
Merged
Merged
Conversation
Pin all GitHub Actions referenced in generated workflows (both first-party `actions/*` and third-party) to immutable commit SHAs. Updating pinned actions is now a deliberate codegen-side bump rather than implicit on every workflow run.
Refresh TypeScript Desktop API SDK from current spec
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
2 participants
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.
The SDK changes on
nextwere not in a release. The published packages were still v5, whilesrc/resources/index.tsandapi.mdonnextalready described app setup, bridge logins, and labels. Simply publishing those changes under the old version would also hide a couple of real upgrade breaks: some exported TypeScript model types moved, andpackages/mcp-server/src/http.ts:29now requires an access token for standalone HTTP requests.This PR sets both package versions to 6.0.0 and keeps the other version-bearing files in step:
src/version.ts:1,packages/mcp-server/src/server.ts:31, and the MCP manifest. A major version lets existing v5 users choose when to upgrade rather than receiving those changes through a v5 range. The release notes show the actual v5-to-v6 differences;app.loginandbridges.connectionsonly existed on unreleasednextbuilds.The release workflow publishes the built packages from the GitHub release without a long-lived npm token.
Tag
@indentto continue the conversation here.