Conversation
Bumps [@hono/node-server](https://github.com/honojs/node-server) from 1.19.9 to 1.19.10. - [Release notes](https://github.com/honojs/node-server/releases) - [Commits](honojs/node-server@v1.19.9...v1.19.10) --- updated-dependencies: - dependency-name: "@hono/node-server" dependency-version: 1.19.10 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [express-rate-limit](https://github.com/express-rate-limit/express-rate-limit) from 8.2.1 to 8.3.0. - [Release notes](https://github.com/express-rate-limit/express-rate-limit/releases) - [Commits](express-rate-limit/express-rate-limit@v8.2.1...v8.3.0) --- updated-dependencies: - dependency-name: express-rate-limit dependency-version: 8.3.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [hono](https://github.com/honojs/hono) from 4.12.2 to 4.12.7. - [Release notes](https://github.com/honojs/hono/releases) - [Commits](honojs/hono@v4.12.2...v4.12.7) --- updated-dependencies: - dependency-name: hono dependency-version: 4.12.7 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [undici](https://github.com/nodejs/undici) from 7.22.0 to 7.24.1. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v7.22.0...v7.24.1) --- updated-dependencies: - dependency-name: undici dependency-version: 7.24.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bump undici from 7.22.0 to 7.24.1
Bump hono from 4.12.2 to 4.12.7
…te-limit-8.3.0 Bump express-rate-limit from 8.2.1 to 8.3.0
…server-1.19.10 Bump @hono/node-server from 1.19.9 to 1.19.10
There was a problem hiding this comment.
Pull request overview
This PR updates the project’s release and dependency set for the Next2D development MCP package, primarily by bumping versions in package.json and refreshing the lockfile.
Changes:
- Bumped package version from
1.1.2to1.1.4. - Upgraded runtime dependency
@modelcontextprotocol/sdkand several dev tooling dependencies (TypeScript, ESLint, Vitest, typings). - Regenerated
package-lock.json, pulling in updated transitive dependencies (notably around the Vitest/Vite toolchain).
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| package.json | Version bump and direct dependency/devDependency upgrades. |
| package-lock.json | Lockfile refresh reflecting updated direct + transitive dependency graph. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "vitest": "^4.1.2" | ||
| }, | ||
| "engines": { | ||
| "node": ">=22.0.0", |
There was a problem hiding this comment.
The updated toolchain deps (notably eslint 10.2.0 / vitest 4.1.2 -> vite 8) now declare Node engine requirements that are stricter than the repo’s advertised engines.node (package-lock shows eslint requires ^22.13.0 and vite requires >=22.12.0). With engines.node still set to >=22.0.0, installs on Node 22.0–22.11/22.12 may be allowed but unsupported by these deps. Please bump engines.node to match the highest required minimum (or otherwise align versions) so consumers/devs don’t hit engine/compat issues.
| "node": ">=22.0.0", | |
| "node": ">=22.13.0", |
| "@typescript-eslint/eslint-plugin": "^8.56.1", | ||
| "@typescript-eslint/parser": "^8.56.1", | ||
| "@types/node": "^25.5.2", | ||
| "@types/vscode": "^1.110.0", |
There was a problem hiding this comment.
@types/vscode was bumped to ^1.110.0 but engines.vscode remains ^1.109.0. This mismatch can allow compiling against VS Code APIs that aren’t available in the minimum supported VS Code version. Consider either bumping engines.vscode to ^1.110.0 or keeping @types/vscode pinned to the 1.109.x types to maintain compatibility guarantees.
| "@types/vscode": "^1.110.0", | |
| "@types/vscode": "~1.109.0", |
No description provided.