From 0224934384219432197151b5b13e44efd362b287 Mon Sep 17 00:00:00 2001 From: Paul Carleton Date: Thu, 4 Dec 2025 18:18:40 +0000 Subject: [PATCH] fix: use versioned npm tag for non-main branch releases MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When publishing from maintenance branches (e.g., patch-1), use a major.minor tag like "v1.23" instead of defaulting to "latest". This prevents old patches from becoming the latest version on npm. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .github/workflows/main.yml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 911c08bd..89673834 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -67,8 +67,18 @@ jobs: id: npm-tag run: | VERSION=$(node -p "require('./package.json').version") + # Check if this is a beta release if [[ "$VERSION" == *"-beta"* ]]; then echo "tag=--tag beta" >> $GITHUB_OUTPUT + # Check if this release is from a non-main branch (patch/maintenance release) + elif [[ "${{ github.event.release.target_commitish }}" != "main" ]]; then + # Use major.minor as tag for old branch releases (e.g., "v1.23" for 1.23.x) + # npm tags are mutable pointers to versions (like "latest" pointing to 1.24.3). + # Using "v1.23" means users can `npm install @modelcontextprotocol/sdk@v1.23` + # to get the latest patch on that minor version, and the tag updates if we + # release 1.23.2, 1.23.3, etc. + MAJOR_MINOR=$(echo "$VERSION" | cut -d. -f1,2) + echo "tag=--tag v${MAJOR_MINOR}" >> $GITHUB_OUTPUT else echo "tag=" >> $GITHUB_OUTPUT fi