chore(deps-dev): take the three devDependency bumps in one tested pass - #29
Merged
Conversation
Dependabot had three open PRs against mcps/fluttersdk-mcp: typescript 6.0.3 to 7.0.2, @types/node 25.9.1 to 26.1.1, and vitest 4.1.7 to 4.1.10. Two are major bumps, and all three would have had to rebase onto the lockfile that #28 rewrote, so they are taken together here and verified once instead of three times. tsc 7 compiles the bridge with no source change, vitest 4.1.10 runs the two bridge tests green, and npm audit still reports 0 vulnerabilities. These are devDependencies only: the published package's runtime dependencies and their declared ranges are untouched.
There was a problem hiding this comment.
Pull request overview
This PR batches three devDependency upgrades for the mcps/fluttersdk-mcp package (TypeScript, Node typings, and Vitest) into a single lockfile refresh, aiming to confirm the build/test pipeline stays green after the major toolchain bumps.
Changes:
- Bump
typescriptfrom^6.0.3to^7.0.2. - Bump
@types/nodefrom^25.9.1to^26.1.1. - Bump
vitestfrom^4.1.7to^4.1.10, updating the lockfile accordingly.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| mcps/fluttersdk-mcp/package.json | Updates the devDependency version ranges for TypeScript, Node typings, and Vitest. |
| mcps/fluttersdk-mcp/package-lock.json | Regenerates the lockfile to reflect the new resolved versions (including transitive updates) after the devDependency bumps. |
Files not reviewed (1)
- mcps/fluttersdk-mcp/package-lock.json: Generated file
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.
What
typescript@types/nodevitestAll three are
devDependencies. The published package's runtime dependencies and their declared ranges are untouched.Why one PR instead of three merges
Every one of those PRs was cut against the lockfile that #28 replaced, so each would have needed a rebase and its own CI cycle, and two of them are major bumps whose only real question is "does the build still pass". Taking them together answers that question once, against the tree that actually exists now.
TypeScript 7 is the interesting one: it compiles
src/with no source change and no new diagnostics.Testing
npm run build(tsc7.0.2): clean, no errors.npm test(vitest4.1.10): 2 tests, both pass.npm audit: 0 vulnerabilities, so the chore(deps): clear 21 Dependabot alerts in the MCP bridge lockfile #28 result holds.typescript7.0.2,@types/node26.1.2,vitest4.1.10,vite8.2.0.Closes #16, closes #15, closes #9.