Skip to content

Conversation

@felixweinberger
Copy link
Contributor

@felixweinberger felixweinberger commented Nov 20, 2025

Summary

  • Adds a step to the publish workflow that detects if the version contains -beta
  • When a beta version is detected, publishes with --tag beta instead of the default latest
  • Stable releases remain unchanged (no --tag argument)

How to use

  1. Update package.json version to e.g., 1.23.0-beta.0
  2. Create PR, approve, merge to main
  3. Create a GitHub Release with tag matching the version 1.23.0-beta.0
  4. Workflow publishes to npm beta tag
  5. Users install via npm install @modelcontextprotocol/sdk@beta

Test plan

  • Create a test release with a beta version to verify the workflow correctly adds --tag beta

When the version in package.json contains "-beta", the publish
workflow will now use `npm publish --tag beta` instead of publishing
to the latest tag. This allows beta versions to be released without
affecting users on the stable channel.
@felixweinberger felixweinberger requested a review from a team as a code owner November 20, 2025 21:35
@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 20, 2025

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/sdk@1146

commit: 4d8927f

@felixweinberger felixweinberger merged commit 33229a4 into main Nov 20, 2025
10 checks passed
@felixweinberger felixweinberger deleted the fweinberger/support-beta-versions branch November 20, 2025 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants