Skip to content

[release] Avoid accidentally releasing the mcp package #3729

Merged
vmarta merged 3 commits intodevelopfrom
vm/mcp-separate-release
Mar 6, 2026
Merged

[release] Avoid accidentally releasing the mcp package #3729
vmarta merged 3 commits intodevelopfrom
vm/mcp-separate-release

Conversation

@vmarta
Copy link
Contributor

@vmarta vmarta commented Mar 6, 2026

Since pwa-kit-mcp package is to be released separately, whenever we bump up the versions of the SDK packages, we need to:

  • avoid bumping up the version of the mcp package
  • and actually downgrading its version to the latest published version (so it won't get published to npm)

How to test drive the PR

Let's try bumping up the SDK versions:

  1. Run npm run bump-version -- 3.20.0 in your terminal
  2. Verify that all the SDK packages are bumped up to the new version
  3. ...except for the MCP package, which will be downgraded to the latest npm version 0.4.0.

The result of bump-version script should look like this:

Ghostty 2026-03-06 at 12 21 16

vmarta added 2 commits March 6, 2026 12:11
During `--package sdk` bumps, lerna version bumps all packages including
`@salesforce/pwa-kit-mcp`. The independent packages are then restored to
their pre-bump versions, but MCP carries a dev version in the repo that
should never appear in a released SDK.

This change restores MCP to its latest published npm version (via
`npm info @latest`) instead of the repo dev version, and moves
`getLatestVersion` to shared utils so it can be reused.
@vmarta vmarta requested a review from a team as a code owner March 6, 2026 20:28
@cc-prodsec
Copy link
Collaborator

cc-prodsec commented Mar 6, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@vmarta vmarta requested review from shethj and vcua-mobify March 6, 2026 20:29
const {location, version: oldVersion} = pkg
const {name, location, version: repoVersion} = pkg
let restoreVersion = repoVersion
if (name === '@salesforce/pwa-kit-mcp') {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dumb question: Instead of restoring a version back, can't we update the bump-version script to skip this package when updating versions ?

Or do we not have control over that since it's lerna driven ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, our script piggy backs on Lerna. So we had to restore the version like that afterwards.

Copy link
Contributor

@shethj shethj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for adding this tweak in. Saves effort during releases 👍

Copy link
Contributor

@vcua-mobify vcua-mobify left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this @vmarta !

@vmarta vmarta enabled auto-merge (squash) March 6, 2026 22:30
@vmarta vmarta merged commit 2855102 into develop Mar 6, 2026
42 checks passed
@vmarta vmarta deleted the vm/mcp-separate-release branch March 6, 2026 22:43
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.

4 participants