Skip to content

chore(deps): bump the all-dependencies group across 1 directory with 7 updates - #200

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot-npm_and_yarn-all-dependencies-51e2304423
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot-npm_and_yarn-all-dependencies-51e2304423

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the all-dependencies group with 7 updates in the / directory:

Package From To
wrangler 4.158.0 4.159.0
@lucide/svelte 1.69.0 1.70.0
@tailwindcss/vite 4.3.4 4.3.5
tailwindcss 4.3.4 4.3.5
vite-plus 1.5.0 1.5.1
undici 7.30.1 8.12.4
ws 8.21.0 8.22.2

Updates wrangler from 4.158.0 to 4.159.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

  • #16737 a589d23 Thanks @​jamesopstad! - Store experimental cf-wrangler dev state in .cloudflare/state

    Persist local resource data in .cloudflare/state relative to the configuration file. Direct Wrangler usage continues to default to .wrangler/state.

  • #16663 fe69809 Thanks @​FlorentCollin! - Add --compatibility flag to wrangler d1 export

    You can now export a remote D1 database that contains virtual tables, such as FTS5 or R*Tree tables:

    wrangler d1 export my-database --remote --output dump.sql --compatibility sqlite3_cli_only

    It accepts d1 (the default) and sqlite3_cli_only. With sqlite3_cli_only, the dump matches the output of the sqlite3 .dump command, including virtual tables. D1 cannot import this dump. sqlite3_cli_only is only supported for remote exports.

  • #16599 dee7a1d Thanks @​petebacondarwin! - Support CLOUDFLARE_AUTH_PROFILE for shared authentication profile selection

    Cloudflare tooling can pass a selected profile to child processes through CLOUDFLARE_AUTH_PROFILE. Explicit profile arguments take precedence over the variable, followed by directory bindings and the default profile. The cf-wrangler development delegate also initializes cf authentication so it reads the selected cf credentials.

    Experimental cf development delegates inherit the selected profile without additional command-line flags. Vite refreshes remote authentication when the resolved profile changes, and cf-wrangler keeps its authentication scoped to the delegate invocation.

  • #15615 c64fdfb Thanks @​svetch! - Support jurisdiction when automatically provisioning D1 databases

    Set jurisdiction on a D1 binding without a database_id to create the database in that jurisdiction during deployment. For example, {"d1_databases":[{"binding":"DB","jurisdiction":"eu"}]} creates an EU-jurisdiction database.

  • #16066 4112820 Thanks @​petebacondarwin! - Add an explicit opt-out for main module imports in generated Worker types

    Use wrangler types --include-main-module=false when the Worker entrypoint is generated build output that should not be type-checked as application source. The corresponding includeMainModule option is available in the experimental type-generation API. The option is preserved by --check and automatic regeneration. Omitting the import opts out of module-derived ctx.exports typing while preserving runtime types, environment bindings, and Durable Object namespace declarations.

    New SvelteKit Workers projects created with C3 use this option so their generated declarations remain stable before and after a build. Imports needed to type Durable Object, service, and Workflow bindings are unaffected.

Patch Changes

  • #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.

  • #16746 abf924e Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

... (truncated)

Commits
  • bf3ec7b Version Packages (#16729)
  • dc4e093 [wrangler] Only mention a verification email when the created address is unve...
  • 56459a5 Update bundled third-party dependencies with known security fixes (#16648)
  • 3ef2afd [wrangler] Delegate Container cleanup to Miniflare (#16413)
  • 6f29f97 Stop persisting account selections made by cf (#16683)
  • fe69809 [wrangler] Add --compatibility flag to d1 export (#16663)
  • 2fb01e7 [deploy-helpers] Warn when dispatch namespace deploys ignore cron triggers (#...
  • c64fdfb [wrangler] Support D1 jurisdiction in automatic provisioning (#15615)
  • a589d23 Store experimental cf-wrangler dev state in .cloudflare/state (#16737)
  • 9b6582c Stop getPlatformProxy() asset misses from recursively calling its own liste...
  • Additional commits viewable in compare view

Updates @lucide/svelte from 1.69.0 to 1.70.0

Release notes

Sourced from @​lucide/svelte's releases.

Version 1.70.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.69.0...1.70.0

Commits

Updates @tailwindcss/vite from 4.3.4 to 4.3.5

Release notes

Sourced from @​tailwindcss/vite'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/vite'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 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 vite-plus from 1.5.0 to 1.5.1

Release notes

Sourced from vite-plus's releases.

vite-plus v1.5.1

Vite+ 1.5.1 fixes two high-severity security issues in package-manager downloads and vp env use, restores interactive input in vp run tasks, fixes vp migrate config merges, and adds a reference page for each package command.

Features

  • Upgrade the bundled Vite and Rolldown (#3390), by @​voidzero-guard[bot] and @​fengmk2:
    • [email protected] to [email protected]. A pnpm install no longer turns every cached build into a cache miss, because Vite tells Vite Task to ignore node_modules/.modules.yaml. It also fixes named imports from Node.js built-ins and reloads in bundled dev mode, subpath imports (#) in the dependency optimizer, SSR builds with build.ssr: true, and chunks shared with workers.
    • [email protected] to [email protected], with module source maps that keep only the sources and names that they trace.
    • @voidzero-dev/vite-plus-core requires postcss@^8.5.32, as the bundled Vite does.

Fixes & Enhancements

  • Security: Vite+ verifies the pnpm that it downloads for its own setup against a hash in the CLI, and checks a downloaded pnpm, Yarn 2+, or bun against the integrity hash in the project's packageManager field instead of the hash that the registry reports. A registry set in a project's .npmrc can no longer make Vite+ run a package manager that does not match (GHSA-5qr3-w62x-jmwx, high). Mirrors and private registries that serve the same package still pass. Each pinned version gets its own cache directory, so a project with a pinned package manager downloads it once more after the upgrade. Unpinned installs keep their current location (#3400), by @​fengmk2 and @​arkmarta.
  • Security: vp env use and other dist-tag lookups, such as pnpm@latest, accept only a valid semver version from the registry, so a registry set in a project's .npmrc can no longer put shell commands into the statements that the vp env use shell wrapper runs (GHSA-p79r-mf8q-r78h, high) (#3395), by @​fengmk2 and @​arkmarta.
  • Scripts that vp run starts get a blocking stdin again when the run block of vite.config.ts is not statically analyzable (for example, a task command held in a constant), so interactive prompts such as vp update --interactive wait for input instead of failing with EAGAIN (#3361), by @​everton-dgn.
  • vp migrate changes only the return statements of a defineConfig callback, so functions inside the config, such as Rolldown codeSplitting.groups[].name callbacks, keep their return values and the build no longer fails. When a callback return cannot receive the merged settings, migration keeps the standalone config files and asks for a manual merge. Pack and task cache migration also recognize configs wrapped in parentheses, as, satisfies, <T>, or ! (#3325, #3372), by @​jong-kyung.
  • vp create react-router passes --no-git-init to create-react-router, so the generator's initial commit no longer stops the Vite+ setup when no Git identity is configured (#3363), by @​chbaefront.
  • env.fish calls fish built-ins through builtin, so vp env use changes the Node.js version even when a user function has the name of a built-in such as count (#3353), by @​naokihaba.
  • Shell completion suggests full command names before aliases, so vp i<Tab> offers install and vp up<Tab> offers update. An alias stays available when no full name matches (#3337), by @​nekomoyi.
  • Completion for vp run and vpr skips comment keys such as "# docs #" in package.json scripts, matches task names that contain :, and shows each task's command as its description in Zsh and Fish (#3354), by @​nekomoyi.
  • vp pm dist-tag rm works with Yarn Berry, because Vite+ passes remove to yarn npm tag (#3358), by @​jong-kyung.

Docs

  • Add a Package Management section to the guide, with a reference page for each of the 38 package commands that lists its options, package-manager support, version requirements, and npm fallbacks. Help output for package commands and the old package management and install URLs point to the new pages (docs) (#3105), by @​jong-kyung.
  • Show the README logo that matches the GitHub theme, so the logo stays visible after a theme change (#3350), by @​fengmk2.

Chore

  • Build Linux native bindings against the napi-cross glibc 2.17 sysroot with @napi-rs/[email protected], let the linker reject unresolved symbols, and run Linux CI on ubuntu-latest again. Let the dependency upgrade workflow change workflow files (#3349, #3384), by @​fengmk2.
  • Refine contributor guidance: AGENTS.md separates the vite-plus package from the global vp CLI and replaces CLAUDE.md, and the Node.js version RFCs describe .nvmrc support (#3388, #3383), by @​liangmiQwQ and @​hyunbinseo.
  • Resolve the docs theme aliases from import.meta.dirname, so the docs dev server no longer warns about __dirname (#3379), by @​liangmiQwQ.
  • Fold the .node-version parse tests into one table (#3355), by @​Brooooooklyn.

Bundled Versions

Tool Version Source Changelog
vite 8.3.7 5def936 8.3.6, 8.3.7
rolldown 1.2.18 f9a49d6 1.2.18
oxc-node 1.0.1 7ff14c3 unchanged
tsdown 0.23.4 npm unchanged
vitest 5.1.0 npm unchanged
oxlint 1.91.0 npm unchanged
oxlint-tsgolint 7.0.2005 npm unchanged
oxfmt 0.76.0 npm unchanged

Upgrade

vp upgrade
</tr></table> 

... (truncated)

Commits
  • e5defe1 release: v1.5.1 (#3401)
  • a110977 fix(pm): verify and content-key managed package-manager installs (#3400)
  • 37cb983 fix(cli): restore blocking stdin after loading a dynamic config (#3361)
  • bb2d43e fix(create): skip React Router Git initialization (#3363)
  • a32a8ce fix(build): use the napi-cross sysroot for native Linux builds (#3349)
  • See full diff in compare view

Updates undici from 7.30.1 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 ws from 8.21.0 to 8.22.2

Release notes

Sourced from ws's releases.

8.22.2

Bug fixes

  • The userinfo of the URL is now percent-decoded (#2352).
  • The WebSocket constructor no longer mutates http: or https: url.URL objects (#2353).

8.22.1

Bug fixes

  • The path of IPC URLs is no longer truncated at : (#2344).

Other notable changes

8.22.0

Features

  • Introduced the protocols option (8b918b01).

Bug fixes

  • Calling websocket.close() with invalid arguments no longer transitions the state to WebSocket.CLOSING (#2337).

8.21.3

Bug fixes

  • The server now correctly rejects permessage-deflate offers if the incoming client_max_window_bits parameter value is smaller than its configured clientMaxWindowBits (e97a20ea).

8.21.2

Bug fixes

  • Fixed a test for CITGM (2eb3be0b).

8.21.1

Bug fixes

... (truncated)

Commits
  • 2582a67 [dist] 8.22.2
  • 3eec252 [perf] Do not retain the read buffer via the close reason (#2354)
  • 9757c69 [fix] Do not modify the url.URL object (#2353)
  • e23d55e [fix] Percent-decode the userinfo of the URL (#2352)
  • 335a610 [perf] Do not retain the read buffer via the frame mask (#2350)
  • f40ccff [doc] Adjust Node.js version requirement in README (#2348)
  • c18a80a [dist] 8.22.1
  • 2ab3d3e [minor] Use http.websocket{M,Unm}ask() if possible (#2347)
  • c9efa88 [ci] Test on node 27
  • aa91518 [test] Skip test on Node.js versions where it does not apply (#2340)
  • Additional commits viewable in compare view

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


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

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

…7 updates

Bumps the all-dependencies group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) | `4.158.0` | `4.159.0` |
| [@lucide/svelte](https://github.com/lucide-icons/lucide/tree/HEAD/packages/svelte) | `1.69.0` | `1.70.0` |
| [@tailwindcss/vite](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-vite) | `4.3.4` | `4.3.5` |
| [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) | `4.3.4` | `4.3.5` |
| [vite-plus](https://github.com/voidzero-dev/vite-plus/tree/HEAD/packages/cli) | `1.5.0` | `1.5.1` |
| [undici](https://github.com/nodejs/undici) | `7.30.1` | `8.12.4` |
| [ws](https://github.com/websockets/ws) | `8.21.0` | `8.22.2` |



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

Updates `@lucide/svelte` from 1.69.0 to 1.70.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.70.0/packages/svelte)

Updates `@tailwindcss/vite` 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-vite)

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 `vite-plus` from 1.5.0 to 1.5.1
- [Release notes](https://github.com/voidzero-dev/vite-plus/releases)
- [Commits](https://github.com/voidzero-dev/vite-plus/commits/v1.5.1/packages/cli)

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

Updates `ws` from 8.21.0 to 8.22.2
- [Release notes](https://github.com/websockets/ws/releases)
- [Commits](websockets/ws@8.21.0...8.22.2)

---
updated-dependencies:
- dependency-name: wrangler
  dependency-version: 4.159.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all-dependencies
- dependency-name: "@lucide/svelte"
  dependency-version: 1.70.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all-dependencies
- dependency-name: "@tailwindcss/vite"
  dependency-version: 4.3.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all-dependencies
- dependency-name: tailwindcss
  dependency-version: 4.3.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all-dependencies
- dependency-name: vite-plus
  dependency-version: 1.5.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: all-dependencies
- dependency-name: undici
  dependency-version: 8.12.4
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: all-dependencies
- dependency-name: ws
  dependency-version: 8.22.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: all-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot
dependabot Bot requested a review from a team November 11, 2026 23:06
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 11, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 15, 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 Nov 15, 2026
@dependabot
dependabot Bot deleted the dependabot-npm_and_yarn-all-dependencies-51e2304423 branch November 15, 2026 17:16

This branch had an error being deployed

1 failed deployment
dependabot[bot]-pr-200 — 27849216 Deployed Nov 11, 2026 by dependabot[bot] via build-and-deploy-preview #256
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants