fix: treat v1.x as primary branch for npm latest tag#1577
Merged
felixweinberger merged 2 commits intomainfrom Feb 24, 2026
Merged
fix: treat v1.x as primary branch for npm latest tag#1577felixweinberger merged 2 commits intomainfrom
felixweinberger merged 2 commits intomainfrom
Conversation
|
@modelcontextprotocol/client
@modelcontextprotocol/server
@modelcontextprotocol/express
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
Releases from v1.x were being published with a release-X.Y npm tag instead of latest, because the workflow only recognized 'main' as the primary branch. This caused npm install @modelcontextprotocol/sdk to resolve to an older version (1.26.0 instead of 1.27.0). Also removes release-v1x.yml which is now redundant and would race with main.yml on v1.x releases.
d9f87cc to
ceea93f
Compare
pcarleton
approved these changes
Feb 24, 2026
felixweinberger
added a commit
that referenced
this pull request
Mar 25, 2026
9 tasks
pcarleton
pushed a commit
that referenced
this pull request
Mar 25, 2026
9 tasks
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
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.
Motivation and Context
Releases from the
v1.xbranch were being published with arelease-X.Ynpm dist-tag instead oflatest. This happened because the publish workflow only recognizedmainas the primary branch, sov1.xwas treated as a maintenance branch. This causednpm install @modelcontextprotocol/sdkto resolve to 1.26.0 instead of 1.27.0.Also removes
release-v1x.ymlwhich is now redundant and would race withmain.ymlon v1.x releases (both trigger for the same release, and whichever publishes first wins).How Has This Been Tested?
Verified the logic change matches the expected behavior: releases from
mainorv1.xgetlatest, releases from other branches getrelease-X.Y.Breaking Changes
None.
Types of changes
Checklist