Refresh stale pnpm dependency graph - #4
Merged
Conversation
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
1 participant
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.
Refreshes the preserved pnpm lock from the current package manifest. The old lock still described the pre-MCP Server dependency graph and pinned vulnerable fast-uri 3.1.0; the regenerated graph matches the current @modelcontextprotocol/server 2.0.0 manifest and removes fast-uri entirely.\n\nValidation:\n- pnpm install --lockfile-only --frozen-lockfile --ignore-scripts\n- bun install --frozen-lockfile\n- bun run test:types\n- bun run test:package\n- git diff --check\n\nThe local full Node and Bun suites were stopped after the existing token-based chunking tests hit their fixed 60-second timeout under this machine; the lock-only diff does not touch runtime source, and protected CI remains the delivery gate.