Skip to content

chore(deps): bump the npm_and_yarn group across 1 directory with 10 updates - #2

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/npm_and_yarn-8d44517cbd
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/npm_and_yarn-8d44517cbd

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 11, 2026

Copy link
Copy Markdown

Bumps the npm_and_yarn group with 10 updates in the / directory:

Package From To
undici 8.11.2 8.12.4
undici 6.29.0 6.29.1
undici 7.30.0 7.30.2
@azure/msal-node 6.0.1 7.2.1
@hono/node-server 2.1.1 2.1.5
@modelcontextprotocol/sdk 1.31.0 1.32.2
@simple-git/argv-parser 1.1.1 2.0.1
fast-uri 3.1.8 3.1.9
fast-xml-parser 5.11.2 5.12.0
mongoose 9.10.3 9.12.1
qs 6.16.0 6.17.1
simple-git 3.36.0 4.0.2

Updates undici from 8.11.2 to 8.12.4

Release notes

Sourced from undici's releases.

v8.12.4

⚠️ Security Fixes

This release fixes six vulnerabilities.

CVE-2026-116592 / GHSA-mqg3-3v4r-cm32 (high)

Undici 8.12.2 and 8.12.3 could cache the final response from a redirect chain under the original request key without applying the origin, cache policy, freshness, or Vary requirements of every intermediate hop. This could poison a cache or expose one user's response to another user. The fix validates every redirect hop, combines their Vary fields, limits freshness and stale serving to the most restrictive hop, and invalidates persistent SQLite entries written by vulnerable releases.

CVE-2026-120474 / GHSA-7xg3-fphp-28hg (medium)

A shared cache used with compose(redirect(), cache()) could store a credential-dependent response from a same-origin redirect under the original URL. A later authenticated or unauthenticated request could then receive another user's response. Redirected requests carrying Authorization, Cookie, or Proxy-Authorization are no longer stored under the original alias key.

CVE-2026-116630 / GHSA-5rm8-gv32-r954 (medium)

A cross-origin redirect during cache revalidation could let a 304 Not Modified response from the redirect target validate a cached response from the original origin. Undici now checks that the revalidation target matches the cached URL and that any returned validator matches the stored representation before replaying the cached body.

CVE-2026-120415 / GHSA-9v6h-8rgp-m69f (medium)

The redirect interceptor did not strip credentials correctly when request headers were supplied as an array of [name, value] pairs. With a header-normalizing interceptor outside redirect(), credentials could be sent to a cross-origin redirect target. Undici now handles both tuple arrays and flat header arrays when removing sensitive headers.

CVE-2026-120222 / GHSA-3g9m-rv3r-w5w2 (medium)

A downstream handler exception during cache replay could escape as an uncaught exception or unhandled promise rejection and terminate the process. This included dump size-limit failures, excessive Content-Encoding values in decompress, asynchronous cache-store failures, and cached-body replay after a 304. These failures are now reported as request errors.

CVE-2026-120423 / GHSA-r4pc-4jcp-7pqc (medium)

fetch() could skip Subresource Integrity verification when valid integrity metadata was separated or surrounded by ASCII whitespace other than a space, including a horizontal tab. Integrity metadata is now split on all ASCII whitespace before SHA-256, SHA-384, or SHA-512 verification.

What's Changed

... (truncated)

Commits
  • 779ee3e Bumped v8.12.4 (#6162)
  • 10fa822 docs: remove security release notes
  • 6228fc5 docs: add security release notes
  • 1dd2657 test(cache): align redirect caching with hop policy
  • 8ea1d61 fix(cache): detect an actual redirect, not a plain revalidation
  • 4257261 test(cache): cover credentialed revalidation refresh
  • aa7ccff fix(cache): treat proxy-authorization as a credential when caching redirects
  • 8cf5ce1 test(cache): cover proxy-authorization credential on same-origin redirect
  • 26c42c2 fix(cache): do not cache credential-bearing same-origin redirects under the a...
  • e958661 test: cover decompress too-many-content-encodings throw on async cache replay
  • Additional commits viewable in compare view

Updates undici from 6.29.0 to 6.29.1

Release notes

Sourced from undici's releases.

v8.12.4

⚠️ Security Fixes

This release fixes six vulnerabilities.

CVE-2026-116592 / GHSA-mqg3-3v4r-cm32 (high)

Undici 8.12.2 and 8.12.3 could cache the final response from a redirect chain under the original request key without applying the origin, cache policy, freshness, or Vary requirements of every intermediate hop. This could poison a cache or expose one user's response to another user. The fix validates every redirect hop, combines their Vary fields, limits freshness and stale serving to the most restrictive hop, and invalidates persistent SQLite entries written by vulnerable releases.

CVE-2026-120474 / GHSA-7xg3-fphp-28hg (medium)

A shared cache used with compose(redirect(), cache()) could store a credential-dependent response from a same-origin redirect under the original URL. A later authenticated or unauthenticated request could then receive another user's response. Redirected requests carrying Authorization, Cookie, or Proxy-Authorization are no longer stored under the original alias key.

CVE-2026-116630 / GHSA-5rm8-gv32-r954 (medium)

A cross-origin redirect during cache revalidation could let a 304 Not Modified response from the redirect target validate a cached response from the original origin. Undici now checks that the revalidation target matches the cached URL and that any returned validator matches the stored representation before replaying the cached body.

CVE-2026-120415 / GHSA-9v6h-8rgp-m69f (medium)

The redirect interceptor did not strip credentials correctly when request headers were supplied as an array of [name, value] pairs. With a header-normalizing interceptor outside redirect(), credentials could be sent to a cross-origin redirect target. Undici now handles both tuple arrays and flat header arrays when removing sensitive headers.

CVE-2026-120222 / GHSA-3g9m-rv3r-w5w2 (medium)

A downstream handler exception during cache replay could escape as an uncaught exception or unhandled promise rejection and terminate the process. This included dump size-limit failures, excessive Content-Encoding values in decompress, asynchronous cache-store failures, and cached-body replay after a 304. These failures are now reported as request errors.

CVE-2026-120423 / GHSA-r4pc-4jcp-7pqc (medium)

fetch() could skip Subresource Integrity verification when valid integrity metadata was separated or surrounded by ASCII whitespace other than a space, including a horizontal tab. Integrity metadata is now split on all ASCII whitespace before SHA-256, SHA-384, or SHA-512 verification.

What's Changed

... (truncated)

Commits
  • 779ee3e Bumped v8.12.4 (#6162)
  • 10fa822 docs: remove security release notes
  • 6228fc5 docs: add security release notes
  • 1dd2657 test(cache): align redirect caching with hop policy
  • 8ea1d61 fix(cache): detect an actual redirect, not a plain revalidation
  • 4257261 test(cache): cover credentialed revalidation refresh
  • aa7ccff fix(cache): treat proxy-authorization as a credential when caching redirects
  • 8cf5ce1 test(cache): cover proxy-authorization credential on same-origin redirect
  • 26c42c2 fix(cache): do not cache credential-bearing same-origin redirects under the a...
  • e958661 test: cover decompress too-many-content-encodings throw on async cache replay
  • Additional commits viewable in compare view

Updates undici from 7.30.0 to 7.30.2

Release notes

Sourced from undici's releases.

v8.12.4

⚠️ Security Fixes

This release fixes six vulnerabilities.

CVE-2026-116592 / GHSA-mqg3-3v4r-cm32 (high)

Undici 8.12.2 and 8.12.3 could cache the final response from a redirect chain under the original request key without applying the origin, cache policy, freshness, or Vary requirements of every intermediate hop. This could poison a cache or expose one user's response to another user. The fix validates every redirect hop, combines their Vary fields, limits freshness and stale serving to the most restrictive hop, and invalidates persistent SQLite entries written by vulnerable releases.

CVE-2026-120474 / GHSA-7xg3-fphp-28hg (medium)

A shared cache used with compose(redirect(), cache()) could store a credential-dependent response from a same-origin redirect under the original URL. A later authenticated or unauthenticated request could then receive another user's response. Redirected requests carrying Authorization, Cookie, or Proxy-Authorization are no longer stored under the original alias key.

CVE-2026-116630 / GHSA-5rm8-gv32-r954 (medium)

A cross-origin redirect during cache revalidation could let a 304 Not Modified response from the redirect target validate a cached response from the original origin. Undici now checks that the revalidation target matches the cached URL and that any returned validator matches the stored representation before replaying the cached body.

CVE-2026-120415 / GHSA-9v6h-8rgp-m69f (medium)

The redirect interceptor did not strip credentials correctly when request headers were supplied as an array of [name, value] pairs. With a header-normalizing interceptor outside redirect(), credentials could be sent to a cross-origin redirect target. Undici now handles both tuple arrays and flat header arrays when removing sensitive headers.

CVE-2026-120222 / GHSA-3g9m-rv3r-w5w2 (medium)

A downstream handler exception during cache replay could escape as an uncaught exception or unhandled promise rejection and terminate the process. This included dump size-limit failures, excessive Content-Encoding values in decompress, asynchronous cache-store failures, and cached-body replay after a 304. These failures are now reported as request errors.

CVE-2026-120423 / GHSA-r4pc-4jcp-7pqc (medium)

fetch() could skip Subresource Integrity verification when valid integrity metadata was separated or surrounded by ASCII whitespace other than a space, including a horizontal tab. Integrity metadata is now split on all ASCII whitespace before SHA-256, SHA-384, or SHA-512 verification.

What's Changed

... (truncated)

Commits
  • 779ee3e Bumped v8.12.4 (#6162)
  • 10fa822 docs: remove security release notes
  • 6228fc5 docs: add security release notes
  • 1dd2657 test(cache): align redirect caching with hop policy
  • 8ea1d61 fix(cache): detect an actual redirect, not a plain revalidation
  • 4257261 test(cache): cover credentialed revalidation refresh
  • aa7ccff fix(cache): treat proxy-authorization as a credential when caching redirects
  • 8cf5ce1 test(cache): cover proxy-authorization credential on same-origin redirect
  • 26c42c2 fix(cache): do not cache credential-bearing same-origin redirects under the a...
  • e958661 test: cover decompress too-many-content-encodings throw on async cache replay
  • Additional commits viewable in compare view

Updates @azure/msal-node from 6.0.1 to 7.2.1

Release notes

Sourced from @​azure/msal-node's releases.

@​azure/msal-node v7.2.1

7.2.1

Fri, 06 Nov 2026 23:13:16 GMT

Patches

  • Bump @​azure/msal-common to v16.16.1 (beachball)

@​azure/msal-node v7.2.0

7.2.0

Thu, 05 Nov 2026 01:03:50 GMT

Minor changes

  • Bump @​azure/msal-common to v16.16.0 (beachball)

Patches

  • Bind interactive browser authorization responses to per-request state #8952 (undefined)

@​azure/msal-node v7.1.2

7.1.2

Tue, 27 Oct 2026 18:15:10 GMT

Patches

  • Bump @​azure/msal-common to v16.15.0 (beachball)

@​azure/msal-node v7.1.1

7.1.1

Wed, 21 Oct 2026 18:37:17 GMT

Patches

  • Bump @​azure/msal-common to v16.14.3 (beachball)

@​azure/msal-node v7.1.0

7.1.0

Tue, 13 Oct 2026 22:26:37 GMT

Minor changes

  • Sanitize authorization code payloads and reject unsupported instance-aware inputs for confidential clients. #8901 ([email protected])

@​azure/msal-node v7.0.2

... (truncated)

Commits
  • 5901161 Update Angular and Vite tooling dependencies (#8976)
  • f0dfcc4 Update Azure Identity in E2E tooling (#8972)
  • 1fbbf4f Fix native token-cache isolation for brokered child requests (#8971)
  • ae17990 Defer sign-in after reset MFA and sign-up/reset JIT (#8973)
  • 9b79aa4 Fix Native Auth V2 error classification (#8961)
  • e1616ab Add Native Auth V2 password reset MFA support (#8963)
  • 403efba Align Native Auth V2 sign-up start with API (#8940)
  • a47ebbf Native Auth V2: add experimental warnings and remove upfront sign-in password...
  • 0d0a031 Post-release PR (#8969)
  • a8a8141 Upgrade compatible dependencies to address security advisories (#8965)
  • Additional commits viewable in compare view

Updates @hono/node-server from 2.1.1 to 2.1.5

Release notes

Sourced from @​hono/node-server's releases.

v2.1.5

What's Changed

New Contributors

Full Changelog: honojs/node-server@v2.1.4...v2.1.5

v2.1.4

What's Changed

Full Changelog: honojs/node-server@v2.1.3...v2.1.4

v2.1.3

Security fixes

serveStatic decodes the request path a second time, leading to bypass of middleware on static paths

Affects: @hono/node-server/serve-static. Fixes serveStatic decoding an already-decoded path, where a crafted request could be routed as one path and served as another, skipping middleware mounted on a static prefix. GHSA-rmxm-3fg6-px4f

serveStatic now rejects request paths that still contain % after decoding. To serve files whose names contain a literal %, set allowPercentInPath: true.

The same fix ships in hono v4.13.11.

v2.1.2

What's Changed

Full Changelog: honojs/node-server@v2.1.1...v2.1.2

Commits
  • 4b47a0d 2.1.5
  • e77824a fix(serve-static): only serve GET and HEAD requests (#405)
  • 1b6e6bf fix(listener): abort the request signal when an HTTP/2 client resets the stre...
  • d57ed9b 2.1.4
  • 92b014c chore: allow hono v5 as a peer dependency (#406)
  • 720ac78 2.1.3
  • 9821792 Merge commit from fork
  • 35bca95 2.1.2
  • 90a2600 fix(listener): avoid mutating response headers when setting Content-Length (#...
  • fe7467c test(request): accept asynchronous body read errors (#403)
  • Additional commits viewable in compare view

Updates @modelcontextprotocol/sdk from 1.31.0 to 1.32.2

Release notes

Sourced from @​modelcontextprotocol/sdk's releases.

1.32.2

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/typescript-sdk@1.32.1...1.32.2

1.32.1

What's Changed

Full Changelog: modelcontextprotocol/typescript-sdk@1.32.0...1.32.1

1.32.0

Upgrade notes

  • Redirects: the HTTP client transports now follow a redirect only when it stays on the same origin (same scheme, host and port; http to https on the same host is allowed). A deployment whose endpoint redirects to another host or port either configures the final URL or sets redirectPolicy: 'follow' on StreamableHTTPClientTransport or SSEClientTransport. In browsers, a redirected request fails unless that option is set.
  • New options, both off unless you set them: maxToolInputElements on McpServer limits the number of array elements and object members in a tool call's arguments. expectedResource on requireBearerAuth accepts only tokens issued for this server (the token's audience).

What's Changed

New Contributors

Full Changelog: modelcontextprotocol/typescript-sdk@1.31.0...1.32.0

Commits
  • 3b73021 chore: bump version to 1.32.2 (#3089)
  • fa56d81 [v1.x] fix: allow registering after connect() when the capability was declare...
  • 6919e95 fix: add explicit | undefined to Transport optional properties (v1.x backport...
  • ff07b00 chore: bump version to 1.32.1 (#2954)
  • 8a74d50 [v1.x] docs: point the README at v2 and say what v1.x supports (#2942)
  • a8cf503 [v1.x] docs: state the principles in CLAUDE.md (#2939)
  • 32549b0 chore: bump version to 1.32.0 (#2935)
  • 588d51d [v1.x] test(e2e): cover tools/call and prompts/get without arguments (#2931)
  • 5a0724d [v1.x] feat(auth): add expectedResource to requireBearerAuth (#2930)
  • 0ca0b62 [v1.x] fix(server): accept tools/call and prompts/get requests that omit argu...
  • Additional commits viewable in compare view

Updates @simple-git/argv-parser from 1.1.1 to 2.0.1

Release notes

Sourced from @​simple-git/argv-parser's releases.

@​simple-git/argv-parser@​2.0.1

Patch Changes

  • 68874c2: Add VISUAL environment variable to set of allowUnsafeEditor environment variables.

    Thanks to @​oss-security-shopify for identifying the vulnerability.

@​simple-git/argv-parser@​2.0.0

Major Changes

  • 98864c6: Updates ahead of the v4 release for simple-git.

    • Adds support for TypeScript declaration maps

    • Exports the isGitEnvKey helper to detect whether an environment variable can be used to configure a git operation

    • Adds detection for includeIf.<condition>.path, thanks to @​NotAFlightRisk for identifying the vulnerability

Patch Changes

  • c427fba: Additional argument parser vulnerability checks:

    • Thanks to @​mrillicit for identifying include.path, filter.*.process
    • Thanks to @​tejas619 for identifying url.*.insteadOf
  • 1bb14df: Vulnerability detection expanded to include pager.*, uploadpack.packObjectsHook, difftool.*.cmd and use of the GIT_CONFIG_PARAMETERS environment variable

    Thanks to @​threalwinky and @​nuc13us for identifying.

  • dfeb116: Vulnerability detection expanded to cover configuration delivered through path-taking global options, where the dangerous value is a file on disk rather than a token simple-git can inspect:

    • --exec-path names the directory git loads built-in commands and remote helpers from, and is blocked under the new allowUnsafeExec category along with the GIT_EXEC_PATH environment variable (previously grouped under allowUnsafeConfigPaths)
    • --git-dir, --work-tree and -C cause git to read the configuration of the repository they name, and are blocked under allowUnsafeConfigPaths

    These options are only detected when supplied before the git sub-command and with a value - used as getters (git.raw('rev-parse', '--git-dir')) or as task options (git.raw('commit', '-C', 'HEAD~1')) they are unaffected.

  • d762810: Add allowUnsafeExec detection to rebase -x and rebase --exec.

    Thanks to @​gdegrange for the vulnerability report.

  • d762810: Add allowUnsafeCommandBinaries detection to configuring trailer.<token>.cmd and trailer.<token>.command.

    Thanks to @​sec-reex for the vulnerability report.

  • Updated dependencies [98864c6]

    • @​simple-git/args-pathspec@​1.0.4
Changelog

Sourced from @​simple-git/argv-parser's changelog.

2.0.1

Patch Changes

  • 68874c2: Add VISUAL environment variable to set of allowUnsafeEditor environment variables.

    Thanks to @​oss-security-shopify for identifying the vulnerability.

2.0.0

Major Changes

  • 98864c6: Updates ahead of the v4 release for simple-git.

    • Adds support for TypeScript declaration maps

    • Exports the isGitEnvKey helper to detect whether an environment variable can be used to configure a git operation

    • Adds detection for includeIf.<condition>.path, thanks to @​bhaswanthc, @​NotAFlightRisk, @​oss-security-shopify for identifying the vulnerability

Patch Changes

  • c427fba: Additional argument parser vulnerability checks:

  • 1bb14df: Vulnerability detection expanded to include pager.*, uploadpack.packObjectsHook, difftool.*.cmd and use of the GIT_CONFIG_PARAMETERS environment variable

    Thanks to @​threalwinky and @​nuc13us for identifying.

  • dfeb116: Vulnerability detection expanded to cover configuration delivered through path-taking global options, where the dangerous value is a file on disk rather than a token simple-git can inspect:

    • --exec-path names the directory git loads built-in commands and remote helpers from, and is blocked under the new allowUnsafeExec category along with the GIT_EXEC_PATH environment variable (previously grouped under allowUnsafeConfigPaths)
    • --git-dir, --work-tree and -C cause git to read the configuration of the repository they name, and are blocked under allowUnsafeConfigPaths

    These options are only detected when supplied before the git sub-command and with a value - used as getters (git.raw('rev-parse', '--git-dir')) or as task options (git.raw('commit', '-C', 'HEAD~1')) they are unaffected.

  • d762810: Add allowUnsafeExec detection to rebase -x and rebase --exec.

    Thanks to @​gdegrange for the vulnerability report.

  • d762810: Add allowUnsafeCommandBinaries detection to configuring trailer.<token>.cmd and trailer.<token>.command.

    Thanks to @​sec-reex for the vulnerability report.

... (truncated)

Commits

Updates fast-uri from 3.1.8 to 3.1.9

Release notes

Sourced from fast-uri's releases.

v3.1.9

Security

This security release fixes four URI parsing and normalization vulnerabilities in fast-uri 3.x. Applications that process untrusted URI input should upgrade to v3.1.9.

  • Medium — URI scheme spoofing through percent-encoded schemes (GHSA-w74x-v6f9-j3xg, CVE-2026-110306): percent-encoded scheme input is now rejected instead of being decoded into a live scheme.
  • Medium — Host confusion during domain-host canonicalization (GHSA-wjr9-j795-jxcr, CVE-2026-110180): malformed domain hosts containing ambiguous delimiters or stripped control characters are now rejected instead of being silently rewritten.
  • Low — Incorrect relative-reference normalization (GHSA-xhq7-xmqj-769h, CVE-2026-110095): dot-segment removal now preserves the resolution semantics of relative references.
  • Low — Scheme injection in suffix references (GHSA-333x-w4r6-6crp, CVE-2026-110725): first-segment colons in path-only suffix references are now escaped so the output is not reparsed as a scheme.

Upgrade with:

npm install [email protected]

Thanks to @​zekth for reporting the scheme, host, and relative-reference issues, and to @​UlisesGascon for finding the suffix-reference issue and reviewing the remediations.

What's Changed

Full Changelog: fastify/fast-uri@v3.1.8...v3.1.9

Commits
  • 0def703 Bumped v3.1.9
  • a1d0da2 test: generate only relative path references
  • 9eb8759 fix: preserve relative paths in suffix and relative resolution
  • 54c30f7 docs: note suffix-reference authority ambiguity
  • 39e6493 fix: escape a first-segment colon in suffix references
  • 745183c test: cover first-segment colon in suffix references
  • ddfc6a5 fix(SEC-03): reject non reg-name characters in domain hosts
  • d86a8d2 fix: keep a colon-first segment behind "./" in relative normalization
  • eb483b5 test: cover colon-first relative references in normalization
  • b110a35 fix(SEC-02): preserve meaning of relative references during normalization
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for fast-uri since your current version.


Updates fast-xml-parser from 5.11.2 to 5.12.0

Release notes

Sourced from fast-xml-parser's releases.

...

Description has been truncated

…pdates

Bumps the npm_and_yarn group with 10 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [undici](https://github.com/nodejs/undici) | `8.11.2` | `8.12.4` |
| [undici](https://github.com/nodejs/undici) | `6.29.0` | `6.29.1` |
| [undici](https://github.com/nodejs/undici) | `7.30.0` | `7.30.2` |
| [@azure/msal-node](https://github.com/AzureAD/microsoft-authentication-library-for-js) | `6.0.1` | `7.2.1` |
| [@hono/node-server](https://github.com/honojs/node-server) | `2.1.1` | `2.1.5` |
| [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk) | `1.31.0` | `1.32.2` |
| [@simple-git/argv-parser](https://github.com/steveukx/git-js/tree/HEAD/packages/argv-parser) | `1.1.1` | `2.0.1` |
| [fast-uri](https://github.com/fastify/fast-uri) | `3.1.8` | `3.1.9` |
| [fast-xml-parser](https://github.com/NaturalIntelligence/fast-xml-parser) | `5.11.2` | `5.12.0` |
| [mongoose](https://github.com/Automattic/mongoose) | `9.10.3` | `9.12.1` |
| [qs](https://github.com/ljharb/qs) | `6.16.0` | `6.17.1` |
| [simple-git](https://github.com/steveukx/git-js/tree/HEAD/simple-git) | `3.36.0` | `4.0.2` |



Updates `undici` from 8.11.2 to 8.12.4
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v8.11.2...v8.12.4)

Updates `undici` from 6.29.0 to 6.29.1
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v8.11.2...v8.12.4)

Updates `undici` from 7.30.0 to 7.30.2
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v8.11.2...v8.12.4)

Updates `@azure/msal-node` from 6.0.1 to 7.2.1
- [Release notes](https://github.com/AzureAD/microsoft-authentication-library-for-js/releases)
- [Commits](AzureAD/microsoft-authentication-library-for-js@msal-node-v6.0.1...msal-node-v7.2.1)

Updates `@hono/node-server` from 2.1.1 to 2.1.5
- [Release notes](https://github.com/honojs/node-server/releases)
- [Commits](honojs/node-server@v2.1.1...v2.1.5)

Updates `@modelcontextprotocol/sdk` from 1.31.0 to 1.32.2
- [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases)
- [Commits](modelcontextprotocol/typescript-sdk@1.31.0...1.32.2)

Updates `@simple-git/argv-parser` from 1.1.1 to 2.0.1
- [Release notes](https://github.com/steveukx/git-js/releases)
- [Changelog](https://github.com/steveukx/git-js/blob/main/packages/argv-parser/CHANGELOG.md)
- [Commits](https://github.com/steveukx/git-js/commits/@simple-git/[email protected]/packages/argv-parser)

Updates `fast-uri` from 3.1.8 to 3.1.9
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](fastify/fast-uri@v3.1.8...v3.1.9)

Updates `fast-xml-parser` from 5.11.2 to 5.12.0
- [Release notes](https://github.com/NaturalIntelligence/fast-xml-parser/releases)
- [Changelog](https://github.com/NaturalIntelligence/fast-xml-parser/blob/master/CHANGELOG.md)
- [Commits](NaturalIntelligence/fast-xml-parser@v5.11.2...v5.12.0)

Updates `mongoose` from 9.10.3 to 9.12.1
- [Release notes](https://github.com/Automattic/mongoose/releases)
- [Changelog](https://github.com/Automattic/mongoose/blob/master/CHANGELOG.md)
- [Commits](Automattic/mongoose@9.10.3...9.12.1)

Updates `qs` from 6.16.0 to 6.17.1
- [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md)
- [Commits](ljharb/qs@v6.16.0...v6.17.1)

Updates `simple-git` from 3.36.0 to 4.0.2
- [Release notes](https://github.com/steveukx/git-js/releases)
- [Changelog](https://github.com/steveukx/git-js/blob/main/simple-git/CHANGELOG.md)
- [Commits](https://github.com/steveukx/git-js/commits/[email protected]/simple-git)

---
updated-dependencies:
- dependency-name: undici
  dependency-version: 8.12.4
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: undici
  dependency-version: 6.29.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: undici
  dependency-version: 7.30.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@azure/msal-node"
  dependency-version: 7.2.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@hono/node-server"
  dependency-version: 2.1.5
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@modelcontextprotocol/sdk"
  dependency-version: 1.32.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: "@simple-git/argv-parser"
  dependency-version: 2.0.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: fast-uri
  dependency-version: 3.1.9
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: fast-xml-parser
  dependency-version: 5.12.0
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: mongoose
  dependency-version: 9.12.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: qs
  dependency-version: 6.17.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: simple-git
  dependency-version: 4.0.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants