Skip to content

build(deps): Bump the dependencies group with 11 updates - #118

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dependencies-2e53e7bb97
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dependencies-2e53e7bb97

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the dependencies group with 11 updates:

Package From To
jose 6.2.15 6.2.17
next 16.4.5 16.4.6
zustand 5.0.16 5.1.0
@cloudflare/vitest-plugin 1.4.0 1.6.1
@playwright/test 1.64.1 1.65.0
@tailwindcss/postcss 4.3.4 4.3.5
@vitejs/plugin-react 6.2.1 6.3.0
eslint-config-next 16.4.5 16.4.6
tailwindcss 4.3.4 4.3.5
vitest 5.0.3 5.1.0
wrangler 4.148.0 4.159.0

Updates jose from 6.2.15 to 6.2.17

Release notes

Sourced from jose's releases.

v6.2.17

Fixes

  • jwt: reject negative maxTokenAge (a5b422c)

v6.2.16

Fixes

  • expose invalid options in general JWS and JWE (e41e54e), closes #920
Changelog

Sourced from jose's changelog.

6.2.17 (2026-11-09)

Fixes

  • jwt: reject negative maxTokenAge (a5b422c)

6.2.16 (2026-11-08)

Fixes

  • expose invalid options in general JWS and JWE (e41e54e), closes #920
Commits
  • 273bec4 chore(release): 6.2.17
  • a5b422c fix(jwt): reject negative maxTokenAge
  • 66a657a chore: cleanup after release
  • 63b80ff chore(release): 6.2.16
  • e41e54e fix: expose invalid options in general JWS and JWE
  • 607c3f7 ci: lock workflow action dependencies
  • c9b739c ci: group monthly dependency updates
  • ecf313b chore(deps-dev): bump workerd in /tap/workerd
  • 961f942 ci: schedule updates on the first monday
  • cd4e496 ci: update shared workflows to v1
  • Additional commits viewable in compare view

Updates next from 16.4.5 to 16.4.6

Release notes

Sourced from next's releases.

v16.4.6

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • [lts-active] Pin Tailwind to 4.3.3 in create-next-app and tests (#101061, #101176) (#101307)
  • [lts-active] Automatically compress route handler responses if not already compressed (#101280)
  • [lts-active] Turbopack GC fixes for dev (#100279, #100370) (#101308)

Credits

Huge thanks to @​lukesandberg and @​eps1lon for helping!

Commits

Updates zustand from 5.0.16 to 5.1.0

Release notes

Sourced from zustand's releases.

v5.1.0

The persist and devtools middleware are improved thanks to @​Tnalxmsk and @​dgesteves!

Release note

  • The persist middleware now supports PromiseLike results from storage reads, migrations, and migration writes. persist.rehydrate() now returns a native Promise<void>, which you can await to ensure hydration is complete.
  • The devtools middleware now supports dispatching store actions directly from Redux DevTools using the new actionCreators option. It also supports nested actions and arguments.

What's Changed

Full Changelog: pmndrs/zustand@v5.0.16...v5.1.0

Commits

Updates @cloudflare/vitest-plugin from 1.4.0 to 1.6.1

Release notes

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

@​cloudflare/vitest-plugin@​1.6.1

Patch Changes

  • #16793 fea323a Thanks @​vicb! - Bump capnp-es to 0.0.17

    This release fixes 3 issues. See the release notes for details.

  • #16683 6f29f97 Thanks @​jamesopstad! - Stop persisting account selections made by cf and the Cloudflare Vite and Vitest plugins

    Profiles continue to select credentials rather than accounts. If the active credentials can access one account, it is selected automatically. If they can access multiple accounts, cf and the Vite and Vitest plugins reuse the selection while running but ask again the next time they start. Configure accountId in cloudflare.config.ts or set the CLOUDFLARE_ACCOUNT_ID environment variable to avoid repeated prompts.

    Wrangler's existing persistent account selection remains unchanged.

  • #16648 56459a5 Thanks @​dario-piotrowicz! - Update bundled third-party dependencies with known security fixes

    Local development and Workers Vitest tests now include security fixes for their bundled dependencies. Local browser rendering also includes security fixes for browser downloads, archive extraction, and proxy support.

    Miniflare and Wrangler now require Node.js 22.12.0 or later, matching the supported runtime range of the new browser installer.

  • #16746 abf924e Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-06

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16792 de10016 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-09

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #15693 307a69a Thanks @​ghostwriternr! - Dispose Miniflare when a Vitest runtime fails to start

    Previously, a Miniflare instance whose startup failed was never disposed, so anything it had already started kept running. If disposal also fails, the original startup error is still reported.

  • #16699 cd24b27 Thanks @​matingathani! - Fix vi.mock() factories failing under Vitest 5.1

    Mock factories in vi.mock() now work when running tests with Vitest 5.1 and later. Previously, any test file that used a mock factory failed during import with asyncLocalStorage.disable() is not implemented.

  • Updated dependencies [fea323a, a589d23, 56459a5, fe69809, abf924e, de10016, abf924e, de10016, 2fb01e7, dee7a1d, dc4e093, cff83d0, 3ef2afd, 4112820, 66bc0d6, cff83d0, 9b6582c, c64fdfb, 4112820]:

@​cloudflare/vitest-plugin@​1.6.0

Minor Changes

  • #16186 f1d81a2 Thanks @​leostera! - Support local Artifacts across Wrangler, Vite, and Workers Vitest

    Set remote: false on an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omitted remote continues to use the deployed resource, with a warning that changes affect real repositories; remote: true explicitly selects it. When remote bindings are disabled (wrangler dev --local, or Vite's remoteBindings: false), Artifacts bindings use the local simulator. Workers Vitest uses the local simulator when remote is omitted, so tests do not change real repositories by accident; set remote: true to test against the deployed resource. Local development does not require Cloudflare credentials, but does require Git 2.32 or newer on the host.

    In Miniflare's own options, Artifacts bindings route like every other binding: only dev.remote: true with a remote proxy connection uses the deployed resource. Wrangler and Vite resolve the deployed-by-default rule, and Workers Vitest its local default, before passing options to Miniflare.

Patch Changes

... (truncated)

Changelog

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

1.6.1

Patch Changes

  • #16793 fea323a Thanks @​vicb! - Bump capnp-es to 0.0.17

    This release fixes 3 issues. See the release notes for details.

  • #16683 6f29f97 Thanks @​jamesopstad! - Stop persisting account selections made by cf and the Cloudflare Vite and Vitest plugins

    Profiles continue to select credentials rather than accounts. If the active credentials can access one account, it is selected automatically. If they can access multiple accounts, cf and the Vite and Vitest plugins reuse the selection while running but ask again the next time they start. Configure accountId in cloudflare.config.ts or set the CLOUDFLARE_ACCOUNT_ID environment variable to avoid repeated prompts.

    Wrangler's existing persistent account selection remains unchanged.

  • #16648 56459a5 Thanks @​dario-piotrowicz! - Update bundled third-party dependencies with known security fixes

    Local development and Workers Vitest tests now include security fixes for their bundled dependencies. Local browser rendering also includes security fixes for browser downloads, archive extraction, and proxy support.

    Miniflare and Wrangler now require Node.js 22.12.0 or later, matching the supported runtime range of the new browser installer.

  • #16746 abf924e Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-06

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16792 de10016 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-09

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #15693 307a69a Thanks @​ghostwriternr! - Dispose Miniflare when a Vitest runtime fails to start

    Previously, a Miniflare instance whose startup failed was never disposed, so anything it had already started kept running. If disposal also fails, the original startup error is still reported.

  • #16699 cd24b27 Thanks @​matingathani! - Fix vi.mock() factories failing under Vitest 5.1

    Mock factories in vi.mock() now work when running tests with Vitest 5.1 and later. Previously, any test file that used a mock factory failed during import with asyncLocalStorage.disable() is not implemented.

  • Updated dependencies [fea323a, a589d23, 56459a5, fe69809, abf924e, de10016, abf924e, de10016, 2fb01e7, dee7a1d, dc4e093, cff83d0, 3ef2afd, 4112820, 66bc0d6, cff83d0, 9b6582c, c64fdfb, 4112820]:

1.6.0

Minor Changes

  • #16186 f1d81a2 Thanks @​leostera! - Support local Artifacts across Wrangler, Vite, and Workers Vitest

    Set remote: false on an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omitted remote continues to use the deployed resource, with a warning that changes affect real repositories; remote: true explicitly selects it. When remote bindings are disabled (wrangler dev --local, or Vite's remoteBindings: false), Artifacts bindings use the local simulator. Workers Vitest uses the local simulator when remote is omitted, so tests do not change real repositories by accident; set remote: true to test against the deployed resource. Local development does not require Cloudflare credentials, but does require Git 2.32 or newer on the host.

    In Miniflare's own options, Artifacts bindings route like every other binding: only dev.remote: true with a remote proxy connection uses the deployed resource. Wrangler and Vite resolve the deployed-by-default rule, and Workers Vitest its local default, before passing options to Miniflare.

... (truncated)

Commits

Updates @playwright/test from 1.64.1 to 1.65.0

Release notes

Sourced from @​playwright/test's releases.

v1.65.0

🥟 Run tests with Bun

The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the --bun flag, because without it bunx playwright test runs on Node.js:

bunx --bun playwright test

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:

  • There is no watch mode. UI mode does not run tests again when files change, and --only-changed does not follow imports.
  • Bun loads modules itself, so --tsconfig and the JSX options in tsconfig.json have no effect, and custom ESM loaders are not supported.
  • Stack traces do not include async frames, and API names do not include the class name: click instead of locator.click. This changes some step locations, step titles and error messages.
  • Console output of a test does not get into the trace and UI mode.

🚨 Reports with only failures

New failures reporter prints failures and successful retries as they occur, followed by a summary, without progress output.

New onlyFailures option of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
reporter: [
['failures'],
['html', { onlyFailures: true }],
],
});

🎯 Test runner

  • New built-in -exclusive- test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:

    test('restart the server', { lock: '-exclusive-' }, async () => {
      // No other test runs while this one is running.
    });
  • test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:

    test('upload a file', async ({ page }) => {
      test.skip('Not implemented yet');
    });

... (truncated)

Commits
  • a1f35e1 chore: mark v1.65.0 (#43925)
  • a99c1ab cherry-pick(#43918): Revert "fix(docker): use latest stable Chrome for Testin...
  • 6f9a7f5 cherry-pick(#43914): docs(release-notes): update Chromium version for 1.65
  • daf93bb cherry-pick(#43912): feat(chromium): roll to r1254
  • 6545e89 cherry-pick(#43902): chore(deps): bump runtime deps
  • 0347448 fix(test runner): track shared ESM dependencies for only-changed (#43837)
  • 86e6924 fix(clock): cancel real-time timer when replay ends paused (#43873)
  • d745ae0 fix(route): wait for all active handlers before disabling interception (#43889)
  • 6e3f5ff docs: release notes for v1.65 (#43874)
  • aa33d27 fix(chromium): honor Linux config directories for channel connections (#43884)
  • Additional commits viewable in compare view

Updates @tailwindcss/postcss from 4.3.4 to 4.3.5

Release notes

Sourced from @​tailwindcss/postcss's releases.

v4.3.5

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)
Changelog

Sourced from @​tailwindcss/postcss's changelog.

[4.3.5] - 2026-11-06

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)
Commits

Updates @vitejs/plugin-react from 6.2.1 to 6.3.0

Release notes

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

plugin-react@6.3.0

Make reactCompilerPreset work with @rolldown/plugin-babel's parallel option (#1549)

reactCompilerPreset now refers to its Babel preset by module path instead of by function, so it can be sent to worker threads.

Changelog

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

6.3.0 (2026-11-09)

Make reactCompilerPreset work with @rolldown/plugin-babel's parallel option (#1549)

reactCompilerPreset now refers to its Babel preset by module path instead of by function, so it can be sent to worker threads.

Commits
  • 0e95069 release: plugin-react@6.3.0 (#1557)
  • 8a7d0d4 feat(plugin-react): make reactCompilerPreset work with @​rolldown/plugin-babel...
  • See full diff in compare view

Updates eslint-config-next from 16.4.5 to 16.4.6

Release notes

Sourced from eslint-config-next's releases.

v16.4.6

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • [lts-active] Pin Tailwind to 4.3.3 in create-next-app and tests (#101061, #101176) (#101307)
  • [lts-active] Automatically compress route handler responses if not already compressed (#101280)
  • [lts-active] Turbopack GC fixes for dev (#100279, #100370) (#101308)

Credits

Huge thanks to @​lukesandberg and @​eps1lon for helping!

Commits

Updates tailwindcss from 4.3.4 to 4.3.5

Release notes

Sourced from tailwindcss's releases.

v4.3.5

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)
Changelog

Sourced from tailwindcss's changelog.

[4.3.5] - 2026-11-06

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)
Commits
  • 9b2c925 4.3.5 (#20672)
  • e0f76e9 Skip the color-mix(…) polyfill without a color interpolation method (#20666)
  • 8c74689 Ignore \<!-- and --> between top-level rules in the CSS parser (#20665)
  • 669fcc1 Don't crash on a color-mix(…) with a single color and no interpolation meth...
  • 7edc50e Canonicalization: don't sort all parsed variants when compiling a single cand...
  • See full diff in compare view

Updates vitest from 5.0.3 to 5.1.0

Release notes

Sourced from vitest's releases.

v5.1.0

   🚀 Features

   🐞 Bug Fixes

Bumps the dependencies group with 11 updates:

| Package | From | To |
| --- | --- | --- |
| [jose](https://github.com/panva/jose) | `6.2.15` | `6.2.17` |
| [next](https://github.com/vercel/next.js) | `16.4.5` | `16.4.6` |
| [zustand](https://github.com/pmndrs/zustand) | `5.0.16` | `5.1.0` |
| [@cloudflare/vitest-plugin](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-plugin) | `1.4.0` | `1.6.1` |
| [@playwright/test](https://github.com/microsoft/playwright) | `1.64.1` | `1.65.0` |
| [@tailwindcss/postcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-postcss) | `4.3.4` | `4.3.5` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `6.2.1` | `6.3.0` |
| [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) | `16.4.5` | `16.4.6` |
| [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) | `4.3.4` | `4.3.5` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.3` | `5.1.0` |
| [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) | `4.148.0` | `4.159.0` |


Updates `jose` from 6.2.15 to 6.2.17
- [Release notes](https://github.com/panva/jose/releases)
- [Changelog](https://github.com/panva/jose/blob/main/CHANGELOG.md)
- [Commits](panva/jose@v6.2.15...v6.2.17)

Updates `next` from 16.4.5 to 16.4.6
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.4.5...v16.4.6)

Updates `zustand` from 5.0.16 to 5.1.0
- [Release notes](https://github.com/pmndrs/zustand/releases)
- [Commits](pmndrs/zustand@v5.0.16...v5.1.0)

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

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

Updates `@tailwindcss/postcss` from 4.3.4 to 4.3.5
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/@tailwindcss-postcss)

Updates `@vitejs/plugin-react` from 6.2.1 to 6.3.0
- [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.3.0/packages/plugin-react)

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

Updates `tailwindcss` from 4.3.4 to 4.3.5
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/tailwindcss)

Updates `vitest` from 5.0.3 to 5.1.0
- [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.1.0/packages/vitest)

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

---
updated-dependencies:
- dependency-name: jose
  dependency-version: 6.2.17
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: next
  dependency-version: 16.4.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: zustand
  dependency-version: 5.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@cloudflare/vitest-plugin"
  dependency-version: 1.6.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@playwright/test"
  dependency-version: 1.65.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@tailwindcss/postcss"
  dependency-version: 4.3.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@vitejs/plugin-react"
  dependency-version: 6.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: eslint-config-next
  dependency-version: 16.4.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: tailwindcss
  dependency-version: 4.3.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: vitest
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: wrangler
  dependency-version: 4.159.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: 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 Nov 13, 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

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