Skip to content

Bump the development group across 1 directory with 16 updates - #177

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/development-f892d06168
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/development-f892d06168

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the development group with 16 updates in the / directory:

Package From To
@anthropic-ai/sdk 0.133.0 0.135.0
@cloudflare/vite-plugin 1.62.5 1.64.0
@modelcontextprotocol/server 2.3.0 2.3.1
@playwright/test 1.63.0 1.64.1
@types/node 26.6.4 26.6.5
@vinext/cloudflare 1.0.1 1.1.1
@vitejs/plugin-react 6.1.1 6.1.2
@vitejs/plugin-rsc 0.5.35 0.5.38
eslint 10.12.0 10.13.0
eslint-config-next 16.3.8 16.4.2
fake-indexeddb 6.2.5 6.2.6
vinext 1.0.1 1.2.1
vite 8.3.2 8.3.4
vitest 5.0.3 5.0.5
wrangler 4.147.0 4.151.0
zod 4.6.5 4.6.7

Updates @anthropic-ai/sdk from 0.133.0 to 0.135.0

Release notes

Sourced from @​anthropic-ai/sdk's releases.

sdk-v0.135.0

Features

  • api: add between_tools to thinking types in model capabilities
  • api: add the speed parameter and usage.speed to Messages
  • api: return a Console organization's usage-tier spend cap as a read-only spend limit

Bug Fixes

  • client: close streams dropped without being read to the end
  • client: keep an unread JSONL response open while it is held

Chores

  • ci: speed up breaking change detection
  • docs: describe headers on Managed Agents and telemetry endpoints

Documentation

  • api: note that some models need a beta header to use speed

sdk-v0.134.0

Features

  • api: add execution_identity to Managed Agents agents

  • api: add organization_type_not_supported error to spend limit lists

  • api: add telemetry destination test endpoint

  • api: add telemetry destinations to the Admin API

  • client: add native support for OpenTelemetry tracing

    If your app registers a global tracer provider, the SDK will create spans with it after upgrading, and they'll be exported with the rest of your traces. Requests will also get trace context headers from the global propagator. To disable, pass openTelemetry: false to the client or set ANTHROPIC_OPEN_TELEMETRY=false. Learn more in the documentation.

Bug Fixes

  • api: rename telemetry destination test response model
  • client: close an unread stream that was dropped while tracing is on
  • client: don't follow redirects on token requests
  • client: treat proxy-authorization as a sensitive header

Bug Fixes

  • streaming: tolerate unknown event types in MessageStream and BetaMessageStream
  • streaming: stop throwing "Unexpected event order" for an event before message_start
  • streaming: yield events that arrive before message_start when iterating MessageStream and BetaMessageStream

... (truncated)

Changelog

Sourced from @​anthropic-ai/sdk's changelog.

0.135.0 (2026-10-15)

Features

  • api: add between_tools to thinking types in model capabilities
  • api: add the speed parameter and usage.speed to Messages
  • api: return a Console organization's usage-tier spend cap as a read-only spend limit

Bug Fixes

  • client: close streams dropped without being read to the end
  • client: keep an unread JSONL response open while it is held

Chores

  • ci: speed up breaking change detection
  • docs: describe headers on Managed Agents and telemetry endpoints

Documentation

  • api: note that some models need a beta header to use speed

0.134.0 (2026-10-14)

Features

  • api: add execution_identity to Managed Agents agents

  • api: add organization_type_not_supported error to spend limit lists

  • api: add telemetry destination test endpoint

  • api: add telemetry destinations to the Admin API

  • client: add native support for OpenTelemetry tracing

    If your app registers a global tracer provider, the SDK will create spans with it after upgrading, and they'll be exported with the rest of your traces. Requests will also get trace context headers from the global propagator. To disable, pass openTelemetry: false to the client or set ANTHROPIC_OPEN_TELEMETRY=false. Learn more in the documentation.

Bug Fixes

  • api: rename telemetry destination test response model
  • client: close an unread stream that was dropped while tracing is on
  • client: don't follow redirects on token requests
  • client: treat proxy-authorization as a sensitive header

Bug Fixes

  • streaming: tolerate unknown event types in MessageStream and BetaMessageStream
  • streaming: stop throwing "Unexpected event order" for an event before message_start

... (truncated)

Commits
  • 04a4c28 release: 0.135.0
  • 69dbe62 Merge pull request #935 from anthropics/synced/published
  • b61a531 feat(helpers): retry a rate-limited fast fallback at standard speed (#943)
  • 38d0ab4 feat(api): add between_tools to thinking types in model capabilities
  • 366b53b chore(docs): describe headers on Managed Agents and telemetry endpoints
  • ca50812 docs(api): note that some models need a beta header to use speed
  • 03f6012 fix(helpers): honor speed overrides from fallback entries when streaming (#942)
  • 88bf034 docs(changelog): shorten the OpenTelemetry tracing note (#941)
  • 7c807a0 fix(client): close streams dropped without being read to the end
  • 64758f6 feat(api): add the speed parameter and usage.speed to Messages
  • Additional commits viewable in compare view

Updates @cloudflare/vite-plugin from 1.62.5 to 1.64.0

Release notes

Sourced from @​cloudflare/vite-plugin's releases.

@​cloudflare/vite-plugin@​1.64.0

Minor Changes

  • #16245 d6b1c82 Thanks @​WalshyDev! - Generate source maps for Worker environments by default

    Worker builds now emit source maps unless Vite's build.sourcemap or the Worker's upload_source_maps is set, so deployed Workers get stack traces that point at the original source. The source maps are written next to the Worker bundle and included in Build Output; the client environment is unchanged, so no source maps are added to public assets. Set build.sourcemap: false for the Worker environment, or upload_source_maps: false in the Worker config, to opt out.

Patch Changes

@​cloudflare/vite-plugin@​1.63.2

Patch Changes

  • #16025 61e07fd Thanks @​kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds

    cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.

  • #16038 dc3e4df Thanks @​dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages

    Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.

  • Updated dependencies [fcf625d, 091e5ec, 5152bf8, 9f87de8, daae435, 18f061c, 9be5ec7, 61e07fd, cafd3f9, ea64ec4, d232454]:

@​cloudflare/vite-plugin@​1.63.1

Patch Changes

  • #15617 93c1069 Thanks @​jpatel3! - Stop the update check from recommending deprecated versions

    Previously, the "update available" notice shown by wrangler and @cloudflare/vite-plugin always pointed at whichever version was tagged latest on npm, even after that version had been deprecated for shipping a bug. Deprecated versions are now never recommended: if the latest release has been deprecated, the newest non-deprecated stable release below it is suggested instead, or nothing at all if you are already on it.

    The check now reads the npm registry directly instead of going through the update-check package, which discarded the deprecation information. The on-disk cache location and one-hour refresh interval are unchanged.

  • #16003 6947df3 Thanks @​oddharsh! - Ship using and await using declarations to the runtime as written

    Worker builds no longer lower explicit resource management into helper code, so Workers that use it ship about 1.7 KB less. workerd supports the syntax natively. On Vite 8 the plugin builds Workers at an es2026 target, so Oxc leaves the syntax alone. On Vite 6 and 7, where esbuild has no es2026 target, the Worker environments tell esbuild that using is supported instead. Client builds keep their own targets: the plugin changes only the Worker environments.

  • #16145 e820406 Thanks @​cpojer! - Honor the source-map setting in release builds

    Omit the plugin's JavaScript and declaration source maps when building with SOURCEMAPS=false, reducing the installed package size. Normal development builds keep source maps, and application source-map settings are unchanged.

  • Updated dependencies [2d1d563, 85b14e7, e6f7663, fe607f9, ad7ff45, 8de6b3c, ae29445, 757faa6, cc8e969, 417b186, 93c1069, 6947df3, 82acf3c, 9a58244]:

@​cloudflare/vite-plugin@​1.63.0

... (truncated)

Changelog

Sourced from @​cloudflare/vite-plugin's changelog.

1.64.0

Minor Changes

  • #16245 d6b1c82 Thanks @​WalshyDev! - Generate source maps for Worker environments by default

    Worker builds now emit source maps unless Vite's build.sourcemap or the Worker's upload_source_maps is set, so deployed Workers get stack traces that point at the original source. The source maps are written next to the Worker bundle and included in Build Output; the client environment is unchanged, so no source maps are added to public assets. Set build.sourcemap: false for the Worker environment, or upload_source_maps: false in the Worker config, to opt out.

Patch Changes

1.63.2

Patch Changes

  • #16025 61e07fd Thanks @​kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds

    cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.

  • #16038 dc3e4df Thanks @​dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages

    Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.

  • Updated dependencies [fcf625d, 091e5ec, 5152bf8, 9f87de8, daae435, 18f061c, 9be5ec7, 61e07fd, cafd3f9, ea64ec4, d232454]:

1.63.1

Patch Changes

  • #15617 93c1069 Thanks @​jpatel3! - Stop the update check from recommending deprecated versions

    Previously, the "update available" notice shown by wrangler and @cloudflare/vite-plugin always pointed at whichever version was tagged latest on npm, even after that version had been deprecated for shipping a bug. Deprecated versions are now never recommended: if the latest release has been deprecated, the newest non-deprecated stable release below it is suggested instead, or nothing at all if you are already on it.

    The check now reads the npm registry directly instead of going through the update-check package, which discarded the deprecation information. The on-disk cache location and one-hour refresh interval are unchanged.

  • #16003 6947df3 Thanks @​oddharsh! - Ship using and await using declarations to the runtime as written

    Worker builds no longer lower explicit resource management into helper code, so Workers that use it ship about 1.7 KB less. workerd supports the syntax natively. On Vite 8 the plugin builds Workers at an es2026 target, so Oxc leaves the syntax alone. On Vite 6 and 7, where esbuild has no es2026 target, the Worker environments tell esbuild that using is supported instead. Client builds keep their own targets: the plugin changes only the Worker environments.

  • #16145 e820406 Thanks @​cpojer! - Honor the source-map setting in release builds

    Omit the plugin's JavaScript and declaration source maps when building with SOURCEMAPS=false, reducing the installed package size. Normal development builds keep source maps, and application source-map settings are unchanged.

  • Updated dependencies [2d1d563, 85b14e7, e6f7663, fe607f9, ad7ff45, 8de6b3c, ae29445, 757faa6, cc8e969, 417b186, 93c1069, 6947df3, 82acf3c, 9a58244]:

... (truncated)

Commits

Updates @modelcontextprotocol/server from 2.3.0 to 2.3.1

Release notes

Sourced from @​modelcontextprotocol/server's releases.

@​modelcontextprotocol/server-legacy@​2.3.1

Patch Changes

  • #2952 5a18673 Thanks @​claude! - requireBearerAuth in @modelcontextprotocol/server-legacy takes the optional expectedResource that @modelcontextprotocol/server 2.3.0 and @modelcontextprotocol/sdk 1.32.0 added: the resource the token must be issued for (its audience), usually the server's URL. When it is set, a token is accepted only if the verifier reports that value in AuthInfo.resource; the two are compared as strings, ignoring a fragment and one trailing slash. A token reported for another value, or for none, is answered 401 invalid_token with the usual WWW-Authenticate challenge. When it is not set, nothing changes. The package stays frozen otherwise; this option is added so that its requireBearerAuth matches the 1.x middleware it is a copy of.

  • Updated dependencies []:

    • @​modelcontextprotocol/core@​2.3.1

@​modelcontextprotocol/server@​2.3.1

Patch Changes

  • Updated dependencies []:
    • @​modelcontextprotocol/core@​2.3.1
Commits
  • fcef852 Version Packages (#2953)
  • e8b7f05 docs: one opening note in the server and client package READMEs (#2955)
  • 5a18673 feat(server-legacy): add expectedResource to requireBearerAuth (#2952)
  • 3ab61c6 docs: update the README banners (#2940)
  • 8aabbdc test(e2e): expect SdkHttpError after a second 401 from onUnauthorized (#2936)
  • 33fecfb test(e2e): cover tools/call without arguments (#2933)
  • 818f782 docs: state the principles in CLAUDE.md and shorten REVIEW.md (#2938)
  • See full diff in compare view

Updates @playwright/test from 1.63.0 to 1.64.1

Release notes

Sourced from @​playwright/test's releases.

v1.64.1

Bug Fixes

  • #43247 [Bug]: _electron.launch intermittently loses a packaged app's first window since 1.64.0
  • #43242 [Regression]: Chromium 155+ aborts a preflighted cross-origin redirect whenever any route is registered (net::ERR_ABORTED)

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');
for (const tool of await page.webmcp.tools())
console.log(tool.name, tool.description);
const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
use: {
video: {
mode: 'on',
size: { width: 1920, height: 1080 },
fps: 60,
show: {
actions: {
style: {
point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
</tr></table>

... (truncated)

Commits
  • cfe490d cherry-pick(#43353): docs: release notes for v1.64 Python
  • 866cbb8 chore: mark v1.64.1 (#43354)
  • 1b29247 cherry-pick(#43250): fix(electron): do not drop windows that have not navigat...
  • 632d976 cherry-pick(#43249): fix(chromium): disable AvoidCorsURLLoaderRestartOnRedirect
  • 824d0c5 cherry-pick(#43217): chore(dotnet): fix async suffix of optional-arg overload...
  • 606ecd8 cherry-pick(#43192): fix(locators): parse locators the way the client API bui...
  • e4f872c cherry-pick(#43188): feat(api): expose asLocatorDescription via LocalUtils fo...
  • f6a439e cherry-pick(#43189): docs(webmcp): expose WebMCP to all languages
  • e2335c3 cherry-pick(#43174): fix(mcp): do not close the browser twice when the client...
  • d2a436e cherry-pick(#43163): Revert "fix(blob): do not remove existing reports from o...
  • Additional commits viewable in compare view

Updates @types/node from 26.6.4 to 26.6.5

Commits

Updates @vinext/cloudflare from 1.0.1 to 1.1.1

Release notes

Sourced from @​vinext/cloudflare's releases.

@​vinext/cloudflare@​1.1.1

Read the Vinext 1.2 release post for the highlights.

Bug Fixes

Cloudflare

  • don't share an in-flight static assets cache index fetch across requests (#3965)
  • never warm through an http-only Worker route (#3931)
  • make --warm-cache-include-fallbacks a no-op (#3906)
  • answer a stored page's conditional request as Next.js does (#3832)
  • never store a conditional request's 304 in the Response Store (#3827)
  • keep Workers Cache off Worker-wide in every generated config (#3820)

Misc

  • Cache: treat x-api-key as a credential for shared response caches (#3879)
  • PPR: key fallback shells apart from the pages of their literal paths (#3891)
  • Cache: key oversized cache identities by a SHA-256 digest (#3876)

Performance

  • Cloudflare: share the pending static assets cache index fetch across requests (#3972)
  • Cloudflare: skip getStaticPaths when Workers Cache revalidates a stored Pages entry (#3960)
  • Pages Router: skip getStaticPaths when Response Store regenerates a stored entry (#3959)

Contributors

@​vinext/cloudflare@​1.1.0

Features

  • Prerender: write a page's special error that escapes the shell with its status (#3716)
  • Response Store: mark tag invalidations stale instead of regenerating them (#3712)
  • Cloudflare: soft-invalidate Workers Cache for stale-while-revalidate invalidations (#3707)

Bug Fixes

App Router

  • stream a special error a Suspense boundary caught as a 200, as Next.js does (#3711)
  • store an RSC-first ISR render with its real status, and never cache unmatched 404s (#3710)
  • store a page's special-error render in the ISR cache (#3702)
  • let only the render decide whether a page is dynamic (#3698)

Cloudflare

  • keep KV entries until their expire (#3735)
  • render Response Store and Workers Cache regenerations and warm-ups whole (#3737)

... (truncated)

Changelog

Sourced from @​vinext/cloudflare's changelog.

1.1.1

Read the Vinext 1.2 release post for the highlights.

Bug Fixes

Cloudflare

  • don't share an in-flight static assets cache index fetch across requests (#3965)
  • never warm through an http-only Worker route (#3931)
  • make --warm-cache-include-fallbacks a no-op (#3906)
  • answer a stored page's conditional request as Next.js does (#3832)
  • never store a conditional request's 304 in the Response Store (#3827)
  • keep Workers Cache off Worker-wide in every generated config (#3820)

Misc

  • Cache: treat x-api-key as a credential for shared response caches (#3879)
  • PPR: key fallback shells apart from the pages of their literal paths (#3891)
  • Cache: key oversized cache identities by a SHA-256 digest (#3876)

Performance

  • Cloudflare: share the pending static assets cache index fetch across requests (#3972)
  • Cloudflare: skip getStaticPaths when Workers Cache revalidates a stored Pages entry (#3960)
  • Pages Router: skip getStaticPaths when Response Store regenerates a stored entry (#3959)

Contributors

1.1.0

Features

  • Prerender: write a page's special error that escapes the shell with its status (#3716)
  • Response Store: mark tag invalidations stale instead of regenerating them (#3712)
  • Cloudflare: soft-invalidate Workers Cache for stale-while-revalidate invalidations (#3707)

Bug Fixes

App Router

  • stream a special error a Suspense boundary caught as a 200, as Next.js does (#3711)
  • store an RSC-first ISR render with its real status, and never cache unmatched 404s (#3710)
  • store a page's special-error render in the ISR cache (#3702)
  • let only the render decide whether a page is dynamic (#3698)

Cloudflare

... (truncated)

Commits
  • b3c6282 chore: version packages (#3789)
  • 1ba87ee perf(cloudflare): share the pending static assets cache index fetch across re...
  • 44c3fad fix(cloudflare): don't share an in-flight static assets cache index fetch acr...
  • 07e7473 perf(cloudflare): skip getStaticPaths when Workers Cache revalidates a stored...
  • db0dee3 perf(pages-router): skip getStaticPaths when Response Store regenerates a sto...
  • 85b5188 fix(cloudflare): never warm through an http-only Worker route (#3931)
  • e94f853 test(cloudflare): store the page when a crawler's conditional request fills a...
  • 43a82db fix(cache): treat x-api-key as a credential for shared response caches (#3879)
  • 5366a7f fix(cloudflare): make --warm-cache-include-fallbacks a no-op (#3906)
  • 608df66 fix(ppr): key fallback shells apart from the pages of their literal paths (#3...
  • Additional commits viewable in compare view

Updates @vitejs/plugin-react from 6.1.1 to 6.1.2

Release notes

Sourced from @​vitejs/plugin-react's releases.

plugin-react@6.1.2

Fix HMR for compound components (#1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

Changelog

Sourced from @​vitejs/plugin-react's changelog.

6.1.2 (2026-10-05)

Fix HMR for compound components (#1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

Commits

Updates @vitejs/plugin-rsc from 0.5.35 to 0.5.38

Release notes

Sourced from @​vitejs/plugin-rsc's releases.

plugin-rsc@0.5.38

Bug Fixes

  • deps: update react 19.3.1 (#1509) (65a1dd5)
  • rsc: skip glob dynamic import specifiers in scan build strip (#1506) (9147ee2)

Continuous Integration

  • rsc: speed up e2e matrix with test subsets and sharding (#1507) (00be872)

plugin-rsc@0.5.37

Features

  • rsc: expose closure captures in transformHoistInlineDirective meta (#1496) (e465056)

Bug Fixes

  • rsc: bind encrypted "use server" closures to their action id (#1499) (e77496b)
  • rsc: drop Server Function source from client sourcemaps (#1497) (6f7c8a1)
  • rsc: keep CSS wrappers out of a trailing comment when a module has no final newline (fix #1495) (#1494) (9a68f29)

Miscellaneous Chores

  • deps: update dependency typescript to v7 (#1422) (443be64)

Tests

  • rsc: remove TEST_SKIP_BUILD from e2e fixture (#1502) (bd74d49)

plugin-rsc@0.5.36

Bug Fixes

  • deps: update all non-major dependencies (#1445) (ee97d2f)
  • deps: update all non-major dependencies (#1486) (98277e7)
  • deps: update dependency es-module-lexer to v3 (#1455) (f4e4a48)
  • deps: update dependency srvx to v1 (#1456) (

Bumps the development group with 16 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@anthropic-ai/sdk](https://github.com/anthropics/anthropic-sdk-typescript) | `0.133.0` | `0.135.0` |
| [@cloudflare/vite-plugin](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vite-plugin-cloudflare) | `1.62.5` | `1.64.0` |
| [@modelcontextprotocol/server](https://github.com/modelcontextprotocol/typescript-sdk) | `2.3.0` | `2.3.1` |
| [@playwright/test](https://github.com/microsoft/playwright) | `1.63.0` | `1.64.1` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.6.4` | `26.6.5` |
| [@vinext/cloudflare](https://github.com/cloudflare/vinext/tree/HEAD/packages/cloudflare) | `1.0.1` | `1.1.1` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `6.1.1` | `6.1.2` |
| [@vitejs/plugin-rsc](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-rsc) | `0.5.35` | `0.5.38` |
| [eslint](https://github.com/eslint/eslint) | `10.12.0` | `10.13.0` |
| [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) | `16.3.8` | `16.4.2` |
| [fake-indexeddb](https://github.com/dumbmatter/fakeIndexedDB) | `6.2.5` | `6.2.6` |
| [vinext](https://github.com/cloudflare/vinext) | `1.0.1` | `1.2.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.3.2` | `8.3.4` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.3` | `5.0.5` |
| [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) | `4.147.0` | `4.151.0` |
| [zod](https://github.com/colinhacks/zod) | `4.6.5` | `4.6.7` |



Updates `@anthropic-ai/sdk` from 0.133.0 to 0.135.0
- [Release notes](https://github.com/anthropics/anthropic-sdk-typescript/releases)
- [Changelog](https://github.com/anthropics/anthropic-sdk-typescript/blob/main/CHANGELOG.md)
- [Commits](anthropics/anthropic-sdk-typescript@sdk-v0.133.0...sdk-v0.135.0)

Updates `@cloudflare/vite-plugin` from 1.62.5 to 1.64.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vite-plugin-cloudflare/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/vite-plugin@1.64.0/packages/vite-plugin-cloudflare)

Updates `@modelcontextprotocol/server` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases)
- [Commits](https://github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/server@2.3.0...@modelcontextprotocol/server@2.3.1)

Updates `@playwright/test` from 1.63.0 to 1.64.1
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.63.0...v1.64.1)

Updates `@types/node` from 26.6.4 to 26.6.5
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@vinext/cloudflare` from 1.0.1 to 1.1.1
- [Release notes](https://github.com/cloudflare/vinext/releases)
- [Changelog](https://github.com/cloudflare/vinext/blob/main/packages/cloudflare/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/vinext/commits/@vinext/cloudflare@1.1.1/packages/cloudflare)

Updates `@vitejs/plugin-react` from 6.1.1 to 6.1.2
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.1.2/packages/plugin-react)

Updates `@vitejs/plugin-rsc` from 0.5.35 to 0.5.38
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-rsc/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-rsc@0.5.38/packages/plugin-rsc)

Updates `eslint` from 10.12.0 to 10.13.0
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v10.12.0...v10.13.0)

Updates `eslint-config-next` from 16.3.8 to 16.4.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](https://github.com/vercel/next.js/commits/v16.4.2/packages/eslint-config-next)

Updates `fake-indexeddb` from 6.2.5 to 6.2.6
- [Release notes](https://github.com/dumbmatter/fakeIndexedDB/releases)
- [Changelog](https://github.com/dumbmatter/fakeIndexedDB/blob/master/CHANGELOG.md)
- [Commits](dumbmatter/fakeIndexedDB@v6.2.5...v6.2.6)

Updates `vinext` from 1.0.1 to 1.2.1
- [Release notes](https://github.com/cloudflare/vinext/releases)
- [Commits](https://github.com/cloudflare/vinext/compare/vinext@1.0.1...vinext@1.2.1)

Updates `vite` from 8.3.2 to 8.3.4
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.3.4/packages/vite)

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)

Updates `wrangler` from 4.147.0 to 4.151.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.151.0/packages/wrangler)

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)

---
updated-dependencies:
- dependency-name: "@anthropic-ai/sdk"
  dependency-version: 0.135.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: "@cloudflare/vite-plugin"
  dependency-version: 1.64.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: "@modelcontextprotocol/server"
  dependency-version: 2.3.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: "@playwright/test"
  dependency-version: 1.64.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: "@types/node"
  dependency-version: 26.6.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: "@vinext/cloudflare"
  dependency-version: 1.1.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: "@vitejs/plugin-react"
  dependency-version: 6.1.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: "@vitejs/plugin-rsc"
  dependency-version: 0.5.38
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: eslint
  dependency-version: 10.13.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: eslint-config-next
  dependency-version: 16.4.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: fake-indexeddb
  dependency-version: 6.2.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: vinext
  dependency-version: 1.2.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: vite
  dependency-version: 8.3.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: vitest
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: wrangler
  dependency-version: 4.151.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: zod
  dependency-version: 4.6.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Oct 19, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T16:20:12.212677Z 9be24f9 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9be24f9088

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread package.json
"vinext": "1.0.1",
"vite": "8.3.2",
"vitest": "^5.0.3",
"vinext": "1.2.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Align React packages with vinext 1.2.1

The upgraded vinext declares react, react-dom, and react-server-dom-webpack peers at ^19.3.1 (package-lock.json lines 11994-11996), but the application still pins React and React DOM to 19.3.0 while the lockfile now resolves the server-components package to 19.3.1. This leaves every vinext build using an unsupported mixed React Server Components release set and produces peer-conflict overrides during installation; upgrade all three React packages together or retain the previous vinext/RSC versions.

AGENTS.md reference: AGENTS.md:L149-L151

Useful? React with 👍 / 👎.

sykosyber added a commit that referenced this pull request Oct 26, 2026
…xc-m3w5)

zod <4.6.6 now carries a high advisory (memory exhaustion validating
oversized constrained collections). It reaches the production tree through
@modelcontextprotocol/client, which dedupes to the root pin, so
`npm audit --omit=dev --audit-level=high` fails until the pin moves.
Same target #177 already proposes; landing it here lets this branch
clear the gate on its own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sykosyber added a commit that referenced this pull request Oct 26, 2026
* Bump the production group across 1 directory with 8 updates

Bumps the production group with 8 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@modelcontextprotocol/client](https://github.com/modelcontextprotocol/typescript-sdk) | `2.2.0` | `2.3.1` |
| [framer-motion](https://github.com/motiondivision/motion) | `14.0.0` | `14.3.0` |
| [idb](https://github.com/jakearchibald/idb) | `8.0.3` | `8.0.4` |
| [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) | `1.52.0` | `1.58.0` |
| [next](https://github.com/vercel/next.js) | `16.3.8` | `16.4.2` |
| [react](https://github.com/react/react/tree/HEAD/packages/react) | `19.3.0` | `19.3.1` |
| [react-dom](https://github.com/react/react/tree/HEAD/packages/react-dom) | `19.3.0` | `19.3.1` |
| [react-server-dom-webpack](https://github.com/react/react/tree/HEAD/packages/react-server-dom-webpack) | `19.3.0` | `19.3.1` |



Updates `@modelcontextprotocol/client` from 2.2.0 to 2.3.1
- [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases)
- [Commits](https://github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/client@2.2.0...@modelcontextprotocol/client@2.3.1)

Updates `framer-motion` from 14.0.0 to 14.3.0
- [Changelog](https://github.com/motiondivision/motion/blob/main/CHANGELOG.md)
- [Commits](motiondivision/motion@v14.0.0...v14.3.0)

Updates `idb` from 8.0.3 to 8.0.4
- [Changelog](https://github.com/jakearchibald/idb/blob/main/CHANGELOG.md)
- [Commits](jakearchibald/idb@v8.0.3...v8.0.4)

Updates `lucide-react` from 1.52.0 to 1.58.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.58.0/packages/lucide-react)

Updates `next` from 16.3.8 to 16.4.2
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.3.8...v16.4.2)

Updates `react` from 19.3.0 to 19.3.1
- [Release notes](https://github.com/react/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react/commits/v19.3.1/packages/react)

Updates `react-dom` from 19.3.0 to 19.3.1
- [Release notes](https://github.com/react/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react/commits/v19.3.1/packages/react-dom)

Updates `react-server-dom-webpack` from 19.3.0 to 19.3.1
- [Release notes](https://github.com/react/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react/commits/v19.3.1/packages/react-server-dom-webpack)

---
updated-dependencies:
- dependency-name: "@modelcontextprotocol/client"
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production
- dependency-name: framer-motion
  dependency-version: 14.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production
- dependency-name: idb
  dependency-version: 8.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: lucide-react
  dependency-version: 1.58.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production
- dependency-name: next
  dependency-version: 16.4.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production
- dependency-name: react
  dependency-version: 19.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: react-dom
  dependency-version: 19.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
- dependency-name: react-server-dom-webpack
  dependency-version: 19.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production
...

Signed-off-by: dependabot[bot] <support@github.com>

* test: mark cancelled animations' finished promise handled under happy-dom

framer-motion 14.3 drives more animations through WAAPI, and happy-dom's
Animation.cancel() rejects `finished` without marking it handled (the Web
Animations spec requires it to be). Stopping an animation mid-flight in
ShellPanel, SettingsPanel and Sidebar tests therefore surfaced 27 unhandled
AbortErrors, failing the run. Patch cancel() once in the vitest setup
instead of mocking framer-motion in yet more test files.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* deps: pin zod 4.6.7 so the production audit gate passes (GHSA-mrhx-c7xc-m3w5)

zod <4.6.6 now carries a high advisory (memory exhaustion validating
oversized constrained collections). It reaches the production tree through
@modelcontextprotocol/client, which dedupes to the root pin, so
`npm audit --omit=dev --audit-level=high` fails until the pin moves.
Same target #177 already proposes; landing it here lets this branch
clear the gate on its own.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Mateo Robles <132870419+sykosyber@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@sykosyber

Copy link
Copy Markdown
Member

@dependabot recreate

@dependabot @github

dependabot Bot commented on behalf of github Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 26, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/development-f892d06168 branch October 26, 2026 00:21
sykosyber added a commit that referenced this pull request Oct 26, 2026
#180)

Same devDependency targets as #177, with the lockfile regenerated after the
production-group bump (#176). #177's own lockfile resolves
react-server-dom-webpack@19.3.1 (via vinext 1.2.1 / @vitejs/plugin-rsc),
which peers react@^19.3.1 while main still pins react@19.3.0, so `npm ci`
fails with ERESOLVE until #176 lands.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant