Repository navigation
fix(deps): refresh lockfile to clear npm audit advisories - #3
Merged
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
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.
Summary
npm run check(and therefore CI onmain) fails at thenpm run auditstep because of published advisories in locked transitive dependencies:body-parser2.3.0 (high) andqs6.16.0 (moderate), via@modelcontextprotocol/sdk→expressfast-uri3.1.8 (moderate), via@modelcontextprotocol/sdk→ajvvitest/@vitest/mocker4.1.11 (moderate, dev only)This PR only refreshes
package-lock.jsonwithnpm audit fix(no--force).package.jsonis unchanged; every bump stays inside the existing semver ranges:Testing
npm cifollowed bynpm run checkpasses locally: lint, 111 tests, build,npm audit(found 0 vulnerabilities) andnpm pack --dry-run.Checklist
npm run checkpasses locally.