Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Frozen installs reject the SDK bump
With
pnpm-lock.yamlstill pinning 1.30.0 for codemode,pnpm install --frozen-lockfilerejects the new 1.31.0 specifier. Pull request and release CI stop before building or testing.Learn more
The codemode lockfile importer still records
@modelcontextprotocol/sdkwith specifier1.30.0and version1.30.0. Both pull request and release workflows use the shared install action, which runspnpm install --frozen-lockfile. That command rejects a manifest whose specifier differs from its lockfile entry, so CI cannot install dependencies.Example: A pull request job checks out this commit and runs the install action. The manifest asks for
1.31.0, the lockfile records1.30.0, and installation fails before the build starts.Recommended fix: Run
pnpm installfrom the repository root and commit the regeneratedpnpm-lock.yamlwith this dependency update.Was this helpful? React with 👍 or 👎 to provide feedback.