Skip to content

Bump the node-dependencies group across 1 directory with 5 updates - #3

Open
dependabot[bot] wants to merge 1 commit into
1.xfrom
dependabot/npm_and_yarn/node-dependencies-a29e274d98
Open

Bump the node-dependencies group across 1 directory with 5 updates#3
dependabot[bot] wants to merge 1 commit into
1.xfrom
dependabot/npm_and_yarn/node-dependencies-a29e274d98

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 24, 2026

Copy link
Copy Markdown

Bumps the node-dependencies group with 5 updates in the / directory:

Package From To
@prefecthq/fastmcp-ts 1.7.3 1.8.1
zod 4.6.5 4.6.7
@biomejs/biome 2.5.15 2.6.2
@vitest/coverage-v8 5.0.3 5.0.5
vitest 5.0.3 5.0.5

Updates @prefecthq/fastmcp-ts from 1.7.3 to 1.8.1

Release notes

Sourced from @​prefecthq/fastmcp-ts's releases.

v1.8.1

Patch Changes

  • 79fdac9: Security update: require @modelcontextprotocol/server, @modelcontextprotocol/server-legacy, and @modelcontextprotocol/client 2.3.1 or later. The previous range (^2.0.0) allowed versions with these advisories:

    • GHSA-jm63-cq47-j5jp (high, server): shared transport or server instances delivered one HTTP client's messages to another.
    • GHSA-46jr-4wx8-v453 (high, server): one HTTP request within the default size limit could exhaust server memory during validation.
    • GHSA-rvq5-wwqv-78pq (medium, server and server-legacy): server bearer authentication accepted tokens issued for another service.
    • GHSA-6prh-2h8m-c8cw (medium, client): HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodies.

    The published CLI inlines its dependency tree, so it now ships the patched SDK: server and server-legacy 2.0.0 -> 2.3.1 (#126, #128), client 2.2.0 -> 2.3.1.

    Also bumps launch-editor 2.14.1 -> 2.14.2 (#124), vite 8.3.0 -> 8.3.4 (#125), and markdown-it 14.3.2 -> 14.3.3 (#127) for security fixes. These are dev-only and do not affect the published package.

v1.8.0

Minor Changes

  • e2cb1d1: Servers that verify tokens from an external authorization server can now publish RFC 9728 protected resource metadata (#114). Wrap a token or request verifier with remoteAuth({ verifier, authorizationServers, baseUrl }) and pass it to auth: the HTTP server serves the document at the path-scoped well-known URL (/.well-known/oauth-protected-resource/mcp for /mcp) and every 401 challenge names it in resource_metadata. The built-in oauth mode now serves its protected resource metadata at the same path-scoped URL and names it in its 401 challenges. The root URL /.well-known/oauth-protected-resource no longer serves it. oauthProvider() now answers an unknown or expired token with 401 invalid_token instead of 500.

Patch Changes

  • d5cb7a5: Fix MCP Apps on the stateless 2025-era HTTP path (#113). fetch() and run({ transport: 'http', stateless: true }) serve each request on a fresh server instance, so only initialize sees the client's capabilities. FastMCP treated every later request as coming from a client without UI support: it removed _meta.ui from tools/list, resources/list and resources/read, and replaced UI tool results with a placeholder. When the client's capabilities are unknown, FastMCP now serves the UI metadata and the real tool result. Clients known to lack UI support still get no UI metadata. For those clients a UI tool now keeps its text content and drops only structuredContent, instead of returning [UI not available in this client]. A UI tool that declares an output schema keeps its structuredContent.
Changelog

Sourced from @​prefecthq/fastmcp-ts's changelog.

1.8.1

Patch Changes

  • 79fdac9: Security update: require @modelcontextprotocol/server, @modelcontextprotocol/server-legacy, and @modelcontextprotocol/client 2.3.1 or later. The previous range (^2.0.0) allowed versions with these advisories:

    • GHSA-jm63-cq47-j5jp (high, server): shared transport or server instances delivered one HTTP client's messages to another.
    • GHSA-46jr-4wx8-v453 (high, server): one HTTP request within the default size limit could exhaust server memory during validation.
    • GHSA-rvq5-wwqv-78pq (medium, server and server-legacy): server bearer authentication accepted tokens issued for another service.
    • GHSA-6prh-2h8m-c8cw (medium, client): HTTP client transports and OAuth requests followed cross-origin redirects and re-sent custom headers and request bodies.

    The published CLI inlines its dependency tree, so it now ships the patched SDK: server and server-legacy 2.0.0 -> 2.3.1 (#126, #128), client 2.2.0 -> 2.3.1.

    Also bumps launch-editor 2.14.1 -> 2.14.2 (#124), vite 8.3.0 -> 8.3.4 (#125), and markdown-it 14.3.2 -> 14.3.3 (#127) for security fixes. These are dev-only and do not affect the published package.

1.8.0

Minor Changes

  • e2cb1d1: Servers that verify tokens from an external authorization server can now publish RFC 9728 protected resource metadata (#114). Wrap a token or request verifier with remoteAuth({ verifier, authorizationServers, baseUrl }) and pass it to auth: the HTTP server serves the document at the path-scoped well-known URL (/.well-known/oauth-protected-resource/mcp for /mcp) and every 401 challenge names it in resource_metadata. The built-in oauth mode now serves its protected resource metadata at the same path-scoped URL and names it in its 401 challenges. The root URL /.well-known/oauth-protected-resource no longer serves it. oauthProvider() now answers an unknown or expired token with 401 invalid_token instead of 500.

Patch Changes

  • d5cb7a5: Fix MCP Apps on the stateless 2025-era HTTP path (#113). fetch() and run({ transport: 'http', stateless: true }) serve each request on a fresh server instance, so only initialize sees the client's capabilities. FastMCP treated every later request as coming from a client without UI support: it removed _meta.ui from tools/list, resources/list and resources/read, and replaced UI tool results with a placeholder. When the client's capabilities are unknown, FastMCP now serves the UI metadata and the real tool result. Clients known to lack UI support still get no UI metadata. For those clients a UI tool now keeps its text content and drops only structuredContent, instead of returning [UI not available in this client]. A UI tool that declares an output schema keeps its structuredContent.
Commits
  • 1baebca chore: version packages (#130)
  • 79fdac9 fix a security issue with mcp server package-lock and also add a chan… (#129)
  • ed0882d Bump @​modelcontextprotocol/server from 2.0.0 to 2.3.1 (#128)
  • 31504ff Bump markdown-it from 14.3.2 to 14.3.3 (#127)
  • 709cfba Bump launch-editor from 2.14.1 to 2.14.2 (#124)
  • 2509473 Bump @​modelcontextprotocol/server-legacy from 2.0.0 to 2.3.1 (#126)
  • 1cd2961 Bump vite from 8.3.0 to 8.3.4 (#125)
  • bc9b688 chore: version packages (#120)
  • e2cb1d1 Feature: Support RFC 9728 (protected resource meta) (#122)
  • d52b262 Bump hono from 4.13.7 to 4.13.13 (#121)
  • Additional commits viewable in compare view

Updates zod from 4.6.5 to 4.6.7

Release notes

Sourced from zod's releases.

v4.6.7

Commits:

  • b500a2ee95134f81d74da7911d7378dd2853d042 4.6.7

v4.6.6

Six malicious commits pushed to main on September 21 with a compromised git credential were reverted the same day in #6620 and have since been removed from the history of main. None were ever published to npm. The npm provenance for 4.6.6 names 284243fb, the pre-rewrite copy of 9c219833 with identical contents.

Commits:

  • 0cd3af5e9f50ad11bbcd4407a46a21b8848ba574 docs: load the en locale directly in Zod Mini
  • 9d5e60f162997b764b40d45aa02481888db50dea docs: import locales from zod/locales, not z.locales
  • 34a626f307871ecbb0123947559328dc52ed5e3e docs: tighten the z.locales tree-shaking note
  • 74304ce5b5796b5edb9a88ceb8e170b6ea3e82df release: stage npm versions instead of publishing them (#6622)
  • b2ef983e0711ff6517d6020b021071e2e5653efa docs: add Code for Japan to bronze sponsors
  • 8fb2faf0584828a6a027d8279db36f6f52784462 docs: crop the Code for Japan logo and list it first in bronze
  • bacad518c41610d654658172d325874bf0ee6290 docs: square the Code for Japan logo to match the other bronze tiles
  • c42596bd1c87e941d7241d10e012c5c196adcc10 release: hold the run on the release-approval environment until the staged versions are approved (#6638)
  • a2ba4a67986a3e6b2b131be30084a2f460d9ea67 fix(types): declare record output and input as members, not base type arguments (#6645)
  • a0ebf970f2d752e5f58527cd2942ff48be4f46bd fix(v4): check array, set and map size bounds before parsing elements (#6652)
  • 529f78dd9431b07f49647fee3aa0819b3f8b66b7 4.6.6
  • 9c219833c3a3764fa1f1ea9c5ecec8254a63c0b1 ci: stage at verbose so a failed OIDC token exchange says why
Commits
  • b500a2e 4.6.7
  • 9c21983 ci: stage at verbose so a failed OIDC token exchange says why
  • 529f78d 4.6.6
  • a0ebf97 fix(v4): check array, set and map size bounds before parsing elements (#6652)
  • a2ba4a6 fix(types): declare record output and input as members, not base type argumen...
  • c42596b release: hold the run on the release-approval environment until the staged ve...
  • bacad51 docs: square the Code for Japan logo to match the other bronze tiles
  • 8fb2faf docs: crop the Code for Japan logo and list it first in bronze
  • b2ef983 docs: add Code for Japan to bronze sponsors
  • 74304ce release: stage npm versions instead of publishing them (#6622)
  • Additional commits viewable in compare view

Updates @biomejs/biome from 2.5.15 to 2.6.2

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.6.2

2.6.2

Minor Changes

  • #11479 5c60ba8 Thanks @​nhedger! - Added a --git flag to biome init. The flag enables Git VCS integration and sets vcs.useIgnoreFile to true in the generated configuration, even when the command runs outside a Git repository.

  • #11742 3a1356d Thanks @​Netail! - Added the biome migrate stylelint command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass --write to apply the changes, and --include-inspired or --include-nursery to migrate additional rules.

  • #12318 774b5b5 Thanks @​Netail! - Added the new assist action useGraphqlSortedDefinitions, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.

    Invalid:

    type User {
  id: ID!
}
enum Role {
ADMIN
USER
}
directive @​auth on FIELD_DEFINITION

  • #6886 3479d15 Thanks @​christymcgrory! - biome rage now shows the resolved files.includes and files.ignoreUnknown configuration.

  • #11102 0874b7f Thanks @​gameroman! - Added support for useTailwindSortedClasses rule in HTML-ish files.

  • #10711 40de5a0 Thanks @​soconnor-seeq! - Adds a new resolutionKind option for object-syntax plugin entries.

    This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.

    {
  "plugins": [
    { "path": "./grit/no-debugger.grit", "resolutionKind": "config" },
    { "path": "local-plugin.grit", "resolutionKind": "project" },
    { "path": "local-plugin.grit" }
  ]
}

    Use resolutionKind: "config" to resolve the plugin from the configuration file that declares it. Use resolutionKind: "project" to resolve the plugin from the consuming project. When omitted, resolutionKind defaults to project. This only affects plugin resolution; includes still apply to end-user project files as usual.

  • #11432 4befd08 Thanks @​ematipico! - Added biome inspect config to show resolved configuration values and their origins as human-readable diagnostics, including matching overrides.

    Configuration files can also extend other configurations up to ten levels deep. Repeated references to the same resolved file are ignored with an information diagnostic, while resolving multiple versions of one extended package produces an error.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.6.2

Minor Changes

  • #11479 5c60ba8 Thanks @​nhedger! - Added a --git flag to biome init. The flag enables Git VCS integration and sets vcs.useIgnoreFile to true in the generated configuration, even when the command runs outside a Git repository.

  • #11742 3a1356d Thanks @​Netail! - Added the biome migrate stylelint command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass --write to apply the changes, and --include-inspired or --include-nursery to migrate additional rules.

  • #12318 774b5b5 Thanks @​Netail! - Added the new assist action useGraphqlSortedDefinitions, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.

    Invalid:

    type User {
  id: ID!
}
enum Role {
ADMIN
USER
}
directive @​auth on FIELD_DEFINITION

  • #6886 3479d15 Thanks @​christymcgrory! - biome rage now shows the resolved files.includes and files.ignoreUnknown configuration.

  • #11102 0874b7f Thanks @​gameroman! - Added support for useTailwindSortedClasses rule in HTML-ish files.

  • #10711 40de5a0 Thanks @​soconnor-seeq! - Adds a new resolutionKind option for object-syntax plugin entries.

    This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.

    {
  "plugins": [
    { "path": "./grit/no-debugger.grit", "resolutionKind": "config" },
    { "path": "local-plugin.grit", "resolutionKind": "project" },
    { "path": "local-plugin.grit" }
  ]
}

    Use resolutionKind: "config" to resolve the plugin from the configuration file that declares it. Use resolutionKind: "project" to resolve the plugin from the consuming project. When omitted, resolutionKind defaults to project. This only affects plugin resolution; includes still apply to end-user project files as usual.

  • #11432 4befd08 Thanks @​ematipico! - Added biome inspect config to show resolved configuration values and their origins as human-readable diagnostics, including matching overrides.

    Configuration files can also extend other configurations up to ten levels deep. Repeated references to the same resolved file are ignored with an information diagnostic, while resolving multiple versions of one extended package produces an error.

  • #11477 ab05554 Thanks @​nhedger! - Added automatic Git VCS integration when running biome init inside a Git repository, including from nested directories and Git worktrees. The generated configuration sets vcs.enabled and vcs.useIgnoreFile to true, with vcs.clientKind set to "git".

... (truncated)

Commits

Updates @vitest/coverage-v8 from 5.0.3 to 5.0.5

Release notes

Sourced from @​vitest/coverage-v8's releases.

v5.0.5

   🐞 Bug Fixes

    View changes on GitHub

v5.0.4

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Updates vitest from 5.0.3 to 5.0.5

Release notes

Sourced from vitest's releases.

v5.0.5

   🐞 Bug Fixes

    View changes on GitHub

v5.0.4

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the node-dependencies group across 1 directory with 5 updates
d67eff7 
Bumps the node-dependencies group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@prefecthq/fastmcp-ts](https://github.com/PrefectHQ/fastmcp-ts) | `1.7.3` | `1.8.1` |
| [zod](https://github.com/colinhacks/zod) | `4.6.5` | `4.6.7` |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.5.15` | `2.6.2` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `5.0.3` | `5.0.5` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.3` | `5.0.5` |



Updates `@prefecthq/fastmcp-ts` from 1.7.3 to 1.8.1
- [Release notes](https://github.com/PrefectHQ/fastmcp-ts/releases)
- [Changelog](https://github.com/PrefectHQ/fastmcp-ts/blob/main/CHANGELOG.md)
- [Commits](PrefectHQ/fastmcp-ts@v1.7.3...v1.8.1)

Updates `zod` from 4.6.5 to 4.6.7
- [Release notes](https://github.com/colinhacks/zod/releases)
- [Commits](colinhacks/zod@v4.6.5...v4.6.7)

Updates `@biomejs/biome` from 2.5.15 to 2.6.2
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/packages/@biomejs/biome/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.6.2/packages/@biomejs/biome)

Updates `@vitest/coverage-v8` from 5.0.3 to 5.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/coverage-v8)

Updates `vitest` from 5.0.3 to 5.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/vitest)

---
updated-dependencies:
- dependency-name: "@prefecthq/fastmcp-ts"
  dependency-version: 1.8.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: node-dependencies
- dependency-name: zod
  dependency-version: 4.6.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: node-dependencies
- dependency-name: "@biomejs/biome"
  dependency-version: 2.6.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: node-dependencies
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: node-dependencies
- dependency-name: vitest
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: node-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 24, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants