Skip to content

fix(deps): update non-major - #1394

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/non-major
Open

renovate[bot] wants to merge 2 commits into
mainfrom
renovate/non-major

Conversation

@renovate

@renovate renovate Bot commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@cloudflare/vitest-plugin (source) ^1.4.10 → ^1.9.0 age confidence devDependencies minor
amannn/action-semantic-pull-request (changelog) 48f2562 → c5e23b7 action digest
davelosert/vitest-coverage-report-action (changelog) 8f86cfb → 74c2d92 action digest
eventsource ^5.1.4 → ^5.1.5 age confidence dependencies patch
knip (source) ^6.43.0 → ^6.47.0 age confidence devDependencies minor
oxfmt (source) ^0.75.0 → ^0.79.0 age confidence devDependencies minor
oxlint (source) ^1.90.0 → ^1.94.0 age confidence devDependencies minor
oxlint-tsgolint ^7.0.2005 → ^7.0.2007 age confidence devDependencies patch 7.0.2008
peter-evans/create-pull-request (changelog) 5f6978f → 3ffccac action digest
pkg-pr-new (source) ^0.0.92 → ^0.0.94 age confidence devDependencies patch
playwright (source) ^1.64.1 → ^1.65.1 age confidence devDependencies minor
rolldown (source) ^1.2.15 → ^1.3.3 age confidence devDependencies minor
undici (source) ^7.30.1 → ^7.30.2 age confidence devDependencies patch

Release Notes

cloudflare/workers-sdk (@​cloudflare/vitest-plugin)

v1.9.0

Compare Source

Minor Changes
  • #​16174 629f135 Thanks @​james-elicx! - Remove the dependency on wrangler

    The Vitest plugin no longer depends on wrangler. Reading the Wrangler configuration file, generating Miniflare options, loading local variables and serving the Pages ASSETS binding now use shared workers-sdk packages that are bundled into the plugin. Installing the plugin no longer installs wrangler as well. If your project runs the wrangler CLI (for example wrangler types), add wrangler to your own devDependencies.

Patch Changes
  • #​17031 95fd4c2 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-19

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

  • #​17043 4f5b118 Thanks @​petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixes

    This patch includes six upstream security fixes covering caching, redirects, and Subresource Integrity verification. Update the shared Undici dependency and matching types together so affected packages ship the patched version.

  • #​17035 1b563db Thanks @​petebacondarwin! - Fix remote bindings authentication with API tokens scoped to an individual Worker

    Remote bindings now create preview sessions through the Worker-scoped endpoint. When the response includes a usable exchange URL, its hostname is used without account-wide Workers subdomain access; otherwise, the existing account subdomain lookup or registration is used. This applies to getPlatformProxy and remote bindings in Wrangler, the Cloudflare Vite plugin, and the Vitest integration. Tokens still need permission to update the named Worker.

  • Updated dependencies [8712fc5, 95fd4c2, 95fd4c2, 8f45554, 4f5b118, 8f45554]:

v1.8.5

Compare Source

Patch Changes
  • #​17003 3595295 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-18

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

  • #​16949 110c162 Thanks @​edmundhung! - Fail remote RPC binding requests on network errors instead of hanging

    Remote bindings that connect over RPC treated every network failure, such as being offline, a DNS or TLS error, as a preview reload. The request then waited silently for a reload that never came. These requests now fail with the error, while GET and HEAD requests interrupted by an actual reload are still retried.

  • #​14578 6750663 Thanks @​penalosa! - Fix Dynamic require errors when importing packages from ES modules

    Importing these packages in a Node.js ES module could fail with Dynamic require of "..." is not supported when a dependency loaded a Node.js built-in. These imports now work without requiring a CommonJS wrapper.

  • Updated dependencies [24bd3c3, 0a4315f, 8f26e90, 3595295, 3595295, f833c8a, 6750663, 67d7c0a, 6750663, 110c162, 5a6e450, 6750663]:

v1.8.4

Compare Source

Patch Changes

v1.8.3

Compare Source

Patch Changes

v1.8.2

Compare Source

Patch Changes

v1.8.1

Compare Source

Patch Changes
  • #​16833 5f539b5 Thanks @​jamesopstad! - Name cf commands and settings in remote bindings errors

    When remote bindings could not authenticate, the error told you to run wrangler whoami, wrangler logout and wrangler login. It now names cf auth whoami, cf auth logout and cf auth login. When a Flagship binding without an id needed to run remotely, the error named Wrangler's app_id setting and suggested wrangler flagship apps create. It now names id and suggests cf flagship apps create.

    For the Vitest plugin, this applies to projects that load cloudflare.config.ts. Projects that use a Wrangler configuration file still see the Wrangler commands.

  • #​16834 8e57331 Thanks @​edmundhung! - Fix test files never finishing when a socket read rejects after a Worker handler has answered

    Previously, if a handler finished while a socket was still being read, for example a database client's connection, the read's rejection could leave vitest run waiting forever after the tests passed. Vitest now reports the unhandled error and the run ends.

  • Updated dependencies [8b2a363, 5f539b5, dc47e6d, 575d136, 3626ee8]:

v1.8.0

Compare Source

Minor Changes
  • #​16682 5966749 Thanks @​ghostwriternr! - Run the Containers that cloudflare.config.ts attaches to Durable Objects

    Previously, projects that load cloudflare.config.ts through the config option ran those Durable Objects without their Containers. The plugin now prepares the Containers' images and runs them, as it does for Wrangler configuration files. Dockerfile and build context paths are relative to the directory that contains cloudflare.config.ts.

    cloudflare.config.ts has no setting that disables local Containers, so, as with the Vite plugin, projects with Container-backed Durable Objects need Docker to run their tests.

Patch Changes
  • #​16824 877b249 Thanks @​jamesopstad! - Move streaming tail consumers to experimental.streamingTailConsumers in cloudflare.config.ts

    Streaming Tail Workers are now declared in a separate, experimental list instead of with streaming: true on a tailConsumers entry. tailConsumers now only lists Tail Workers with a tail() handler. This is a breaking change to the experimental config API: move each entry that set streaming: true to experimental.streamingTailConsumers, without the streaming field.

    export default defineConfig({
      worker: {
        tailConsumers: [{ worker: "tail-worker" }],
        experimental: {
          streamingTailConsumers: [{ worker: "streaming-tail-worker" }],
        },
      },
    });

    Fields under experimental may change or be removed without a major version bump. The wrangler-to-cf codemod now converts streaming_tail_consumers to experimental.streamingTailConsumers.

  • #​16734 c47cca7 Thanks @​matingathani! - Fix CommonJS dependencies being loaded as ES modules under Vitest 5 inline projects

    A dependency with its own "type": "commonjs" package.json was treated as an ES module when an earlier .js file elsewhere in the project had been classified by the project's "type": "module" package.json. The dependency then failed at import with errors such as Cannot set properties of undefined or exports is not defined. The nearest package.json now always decides how a .js file is loaded.

  • Updated dependencies [877b249, 69e650c]:

v1.7.0

Compare Source

Minor Changes
  • #​15695 d437be3 Thanks @​ghostwriternr! - Run the Containers that the Wrangler configuration attaches to Durable Objects

    Previously, the plugin disabled Containers, so those Durable Objects ran without ctx.container. The plugin now builds or pulls the Containers' images before each project's tests run and gives the Durable Objects a real ctx.container, so these projects now need Docker. To keep running their tests without Docker, set dev.enable_containers to false in the Wrangler configuration, which disables the Containers. Cloudflare-managed registry images are not supported yet.

Patch Changes

v1.6.1

Compare Source

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]:

v1.6.0

Compare Source

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
  • #​16700 dc35efb Thanks @​cjol! - Bump bundled brace-expansion to pick up security fixes

    These packages bundle brace-expansion (a dependency of minimatch), and the bundled versions were affected by published advisories. The bundles now include brace-expansion 2.1.7 (from 2.0.1) and 5.0.12 (from 5.0.5). Normal glob patterns expand as before; only the pathological patterns targeted by the advisories are handled differently.

  • #​16700 dc35efb Thanks @​cjol! - Bump bundled devalue from 5.6.3 to 5.9.3 to pick up security fixes

    devalue is bundled into these packages, which use it to serialise values between Node.js and workerd. Version 5.6.3 is affected by several published advisories, and 5.9.3 includes their fixes. Serialisation behaviour does not change.

  • #​16700 dc35efb Thanks @​cjol! - Bump bundled minimatch from 5.1.6 to 5.1.9 to pick up security fixes

    These packages bundle minimatch, and 5.1.6 is affected by published ReDoS advisories. Version 5.1.9 includes the fixes. 5.1.8 is skipped because it broke recursive ** matching, which D1's migrations_pattern relies on.

  • #​16695 b2061f4 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-04

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

  • Updated dependencies [dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, b8387a5, fa3edb3, 4cde694, b2061f4, b2061f4, f1d81a2, 4bb491b, 36e64f2, 92c4b97]:

v1.5.1

Compare Source

Patch Changes
  • #​16670 b14b9dc Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-03

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

  • #​16609 da26b7f Thanks @​gpanders! - Fix tests failing to start with resolve.preserveSymlinks in isolated node_modules layouts

    With resolve.preserveSymlinks: true in a pnpm project, tests failed to start with No such module ".../node_modules/vitest/dist/chai", because a package's own dependencies are linked only next to its real path. Packages linked from a store inside node_modules now load from their real paths, and other files keep their symlinked paths.

  • Updated dependencies [b14b9dc, 44d1ee4, b14b9dc, d2eda1c, 2750917, 34f34b3]:

v1.5.0

Compare Source

Minor Changes
  • #​16424 1598fd3 Thanks @​edmundhung! - Promote experimental.newConfig to a stable config option

    The experimental experimental.newConfig option is now the stable config option. Pass config: true to cloudflareTest() to load your Worker's bindings, entrypoint and compatibility settings from cloudflare.config.ts in the project root, or pass the path of a cloudflare.config.ts elsewhere:

    cloudflareTest({ config: true });
    cloudflareTest({ config: "./worker/cloudflare.config.ts" });

    config can't be combined with wrangler. miniflare options are merged over the Worker from cloudflare.config.ts, with miniflare values taking precedence. Config functions receive Vitest's mode as ctx.mode, which defaults to test and can be changed with --mode.

    If you're moving from experimental.newConfig, secrets are now read from Vite's envDir instead of the directory containing cloudflare.config.ts, and remote bindings authenticate with cf instead of Wrangler.

Patch Changes
  • #​16642 d38cb02 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-02

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

  • #​16623 51bbf8b Thanks @​petebacondarwin! - Deprecate shared tooling helper exports from Miniflare

    Miniflare continues to export getNodeCompat, NodeJSCompatMode, and getFreshSourceMapSupport for compatibility. These exports are deprecated and now use the implementations in @cloudflare/workers-utils. Add a dependency on that package and replace the Miniflare imports with:

    import {
      getNodeCompat,
      type NodeJSCompatMode,
    } from "@cloudflare/workers-utils/node-compat";
    import { getFreshSourceMapSupport } from "@cloudflare/workers-utils/sourcemap";

    Wrangler and the Cloudflare Vite and Vitest plugins now use the shared helpers directly. The helpers retain their behavior and can be imported without loading the Workers runtime.

    The deprecated Miniflare exports will be removed in a later release, allowing downstream tools such as cf to migrate and release independently first.

  • Updated dependencies [d38cb02, d38cb02, 51bbf8b, e5b1798]:

v1.4.12

Compare Source

Patch Changes

v1.4.11

Compare Source

Patch Changes
  • #​15565 142230d Thanks @​luccamordente! - Flush console.log() calls made from another I/O context without waiting for the runner's next message

    Vitest awaits every RPC call it made before it reports a test file as finished. A console.log() from another I/O context (a handler reached through SELF, a queue consumer, a waitUntil() callback) is buffered and sent with the runner's next message, so a log with nothing from the runner following it — the last batch of a queue consumed as the file ends, for example — left the run waiting on itself: the file's tests passed and vitest never finished. The buffer is now flushed from the runner's context as soon as a log is buffered.

  • #​16013 [8b64bec](https://r

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 3am on the first day of the month"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@renovate
renovate Bot requested a review from a team November 1, 2026 02:14
@vercel

vercel Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
tsdocs-client Ignored Ignored Nov 21, 2026 11:16pm UTC

Request Review

@github-actions

github-actions Bot commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 85.19% 2060 / 2418
🔵 Statements 85.08% 2162 / 2541
🔵 Functions 83.45% 585 / 701
🔵 Branches 84.2% 1567 / 1861
File CoverageNo changed files found.
Generated in workflow #5628 for commit 05fae79 by the Vitest Coverage Report Action

@github-actions

github-actions Bot commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

📚 TypeDoc Generation Result

✅ TypeDoc generated successfully!

  • File size: 16M
  • Total exports: 271
  • Artifact: typedoc-44e004bb9232eeb025048903e80bb84adccecc9d
  • HTML docs preview: Download artifact

The TypeDoc JSON file has been generated and validated. All documentation scripts completed successfully.

@renovate
renovate Bot force-pushed the renovate/non-major branch 5 times, most recently from 5f4df5c to 72c3648 Compare November 4, 2026 07:35
@socket-security

socket-security Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedgithub/​davelosert/​vitest-coverage-report-action@​8f86cfb56ed6d5613ea8cdc5259f207fbfd51ece ⏵ 74c2d9210b4fc44c84d8213f61d7ec99837b7aa0100 +1100100100100

View full report

@renovate
renovate Bot force-pushed the renovate/non-major branch 10 times, most recently from b623a73 to 8c21195 Compare November 9, 2026 20:59
@renovate renovate Bot changed the title chore(deps): update non-major fix(deps): update non-major Nov 9, 2026
squiggler-app Bot added a commit that referenced this pull request Nov 9, 2026
@renovate
renovate Bot force-pushed the renovate/non-major branch from 3a12a79 to 6064fe0 Compare November 10, 2026 13:03
@renovate
renovate Bot force-pushed the renovate/non-major branch from 53373a8 to 12ab06f Compare November 10, 2026 23:54
@renovate
renovate Bot force-pushed the renovate/non-major branch from 2911420 to 88d1494 Compare November 11, 2026 16:38
@renovate
renovate Bot force-pushed the renovate/non-major branch from 9322a29 to ca3145f Compare November 12, 2026 17:05
@renovate
renovate Bot force-pushed the renovate/non-major branch from 4f5a2dc to e86807c Compare November 13, 2026 22:00
@renovate
renovate Bot force-pushed the renovate/non-major branch from 7846e02 to 0b92eae Compare November 15, 2026 00:09
@renovate
renovate Bot force-pushed the renovate/non-major branch from ead4e41 to b6d1bd4 Compare November 16, 2026 16:24
@renovate
renovate Bot force-pushed the renovate/non-major branch from 612f475 to 6cf3be4 Compare November 17, 2026 10:43
@renovate
renovate Bot force-pushed the renovate/non-major branch from 340cb5b to c24f6ea Compare November 17, 2026 10:45
@renovate
renovate Bot force-pushed the renovate/non-major branch from c5f590b to 48f10f6 Compare November 17, 2026 23:11
@renovate
renovate Bot force-pushed the renovate/non-major branch from 33e99e8 to f613d5a Compare November 18, 2026 15:06
@renovate
renovate Bot force-pushed the renovate/non-major branch from 213ebc2 to 6715eb3 Compare November 19, 2026 11:22
@renovate
renovate Bot force-pushed the renovate/non-major branch from d3b4696 to 2a64603 Compare November 19, 2026 21:51
@renovate
renovate Bot force-pushed the renovate/non-major branch from 64e64a2 to 2579dc6 Compare November 20, 2026 07:34
@renovate
renovate Bot force-pushed the renovate/non-major branch from 8dfef91 to 92640ce Compare November 21, 2026 01:57
@renovate
renovate Bot force-pushed the renovate/non-major branch from d94956b to f4b7807 Compare November 21, 2026 14:56
@renovate
renovate Bot force-pushed the renovate/non-major branch from 6fa2a4a to de478f5 Compare November 21, 2026 23:16

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants