Skip to content

fix(deps): update vitest, playwright and workerd - #302

Open
tbhb-dev-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vitest-playwright-and-workerd
Open

tbhb-dev-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vitest-playwright-and-workerd

Conversation

@tbhb-dev-renovate

@tbhb-dev-renovate tbhb-dev-renovate Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vitest-plugin (source) 1.6.1 → 1.8.2 age confidence
playwright (source) 1.65.0 → 1.65.1 age confidence
playwright-core (source) 1.65.0 → 1.65.1 age confidence
wrangler (source) 4.159.0 → 4.162.0 age confidence

Move the pins in playwright/private/browsers.bzl to the new playwright-core's browsers.json on this branch: PLAYWRIGHT_VERSION, the chromium-headless-shell revision and browser version, and each archive's URL and sha256. Until then launch_test in playwright/e2e/smoke and //tests:versions_test in storybook fail, as expected.

Regenerate both smoke Workers' types on this branch before merging: cd cloudflare/e2e/smoke && bazel run //:worker_types_test.update && bazel run //nested:worker_types_test.update, then commit both worker-configuration.d.ts files. Until then both worker_types_test targets fail, as expected.


Release Notes

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

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
microsoft/playwright (playwright)

v1.65.1

Compare Source

Bug Fixes
  • #​43936 [Regression]: decorated class with a static field fails to load in 1.65 ("_initClass is not a function") with useDefineForClassFields: false
  • #​43934 [Bug]: Test locations are one column off under Bun 1.4.4+
Browser Versions
  • Chromium 159.0.8154.6
  • Mozilla Firefox 159.0
  • WebKit 27.2
cloudflare/workers-sdk (wrangler)

v4.162.0

Compare Source

Minor Changes
  • #​16735 f005593 Thanks @​leostera! - Use the local simulator for Artifacts bindings that omit remote

    Behavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted remote in Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos in wrangler dev or vite dev, set "remote": true on the binding (dev: { remote: true } in cloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.

    While remote is omitted, wrangler dev, getPlatformProxy() and the Vite plugin warn when remote bindings are enabled, once for each binding rather than on every config reload: "Artifacts binding REPOS uses the local simulator by default. Set remote: true to use deployed repos, or remote: false to silence this warning." Workers Vitest and wrangler dev --local already used the simulator, so they don't warn. Local Artifacts needs no Cloudflare credentials, but requires Git 2.32 or newer on the host.

  • #​16749 032f8c2 Thanks @​vaishnav-mk! - Reject settings on a workflows binding to a Workflow declared in exports

    A workflows binding can still bind a Workflow that the Worker declares in exports, but it can no longer set limits, concurrency, schedules, default_retention, or jurisdiction for it. Set them on the export instead. Previously the binding and the export could both set them as long as they agreed, so configurations that set them on the binding now stop with an error that says which setting to move.

  • #​16749 032f8c2 Thanks @​vaishnav-mk! - Upload Workflow export settings with the Worker

    wrangler deploy and wrangler versions upload now include the settings of each workflow export (limits, concurrency, schedules, default_retention, and jurisdiction) in the upload, instead of sending only its type and name. Uploads of a Worker with workflow exports also send a Cloudflare-Workers-Script-Api-Date header, which lets the Workers API provision Workflow exports from these settings as part of the upload. wrangler deploy and wrangler triggers deploy still create or update each Workflow through the Workflows API afterwards, as before.

    If provisioning a scheduled Workflow fails because the account is on the free plan, wrangler deploy now explains that scheduled Workflows require a paid Workers plan.

Patch Changes
  • #​16849 3cea40b Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-12

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

  • #​16886 63eb6da Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-13

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

  • #​16849 3cea40b Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261110.1 ^5.20261112.1
    workerd 1.20261110.1 1.20261112.1
  • #​16886 63eb6da Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261112.1 ^5.20261113.1
    workerd 1.20261112.1 1.20261113.1
  • #​16864 3b1b408 Thanks @​MattieTK! - Fix packages with nested package.json files missing from deploy metadata

    Packages such as hono, stripe and @modelcontextprotocol/sdk were silently omitted from the package dependency metadata reported during wrangler deploy and wrangler versions upload. These packages are now included with their installed versions. Autoconfig and codemods also detect their installed versions correctly.

  • #​16862 c889551 Thanks @​petebacondarwin! - Fix requests hanging when a local Worker reload finishes before an inflight request fails

    Wrangler now immediately processes retriable requests when the replacement Worker is already ready. Previously, these requests could remain queued until another request arrived, particularly on Windows where connection failures can take longer to report.

  • Updated dependencies [f005593, 61eacca, 856842e, 856842e, 3cea40b, 63eb6da, 3cea40b, 63eb6da]:

v4.161.0

Compare Source

Minor Changes
  • #​16840 8b2a363 Thanks @​jamesopstad! - Write source maps in Build Output with sources relative to each source map file

    This changes the experimental Build Output that wrangler build --experimental-cf-build-output and cf-wrangler build write. Their source maps were prepared as if for upload, with sources relative to the project root. For Workers that Wrangler does not bundle, leading ../ segments were also removed, which lost the location of some files. They now point from each source map's location in bundle/ to the original files, like the source maps the Vite plugin writes.

Patch Changes
  • #​16833 5f539b5 Thanks @​jamesopstad! - Name cf commands and cloudflare.config.ts settings in remote bindings errors from cf-wrangler

    When cf runs development through the cf-wrangler delegate and remote bindings cannot be authenticated, the error now tells you to run cf auth whoami, cf auth logout and cf auth login instead of the Wrangler commands, and the Cloudflare Access hint names cf. The Flagship error for a binding whose app has not been created now names the binding's id setting instead of app_id, and suggests cf flagship apps create. wrangler dev still names Wrangler's commands and settings.

  • #​16527 dc47e6d Thanks @​petebacondarwin! - Normalize relative redirect pathnames consistently across Pages and Workers assets

    Relative _redirects targets now use shared pathname normalization after placeholder replacement, keeping repeated separators within the site's path. Explicit external targets (including scheme-less URLs such as //example.com/path), query values and fragments retain their contents.

  • #​16559 575d136 Thanks @​edmundhung! - Update @netlify/build-info to 11.3.1

  • #​16838 3626ee8 Thanks @​jamesopstad! - Keep the remote bindings session when you remove the last remote binding

    When you removed the last remote binding while wrangler dev was running, Wrangler restarted the remote bindings session with credentials that ignored --profile and the account_id in your Wrangler config. So it could use a different account or ask you to choose one. Wrangler now keeps the existing session, and starts a new one with your current credentials when you add a remote binding again.

  • Updated dependencies [dc47e6d]:

v4.160.1

Compare Source

Patch Changes

v4.160.0

Compare Source

Minor Changes
  • #​16760 cb9534f Thanks @​petebacondarwin! - Support forwarded Wrangler development server options in the experimental cf-wrangler delegate

    cf dev can now forward options such as --inspector-port 9229, --ip, --var, and --persist-to to the Wrangler development runtime. The delegate reuses Wrangler's dev option definitions and validation while retaining project config discovery, --mode environment selection, local development, and its .cloudflare/state default. Invalid option combinations produce a single-line usage error and exit code 2 before starting the server.

    Place server options that overlap cf's global options after --, for example cf dev -- --local --persist-to "custom state". Config and script overrides, whole-worker remote development, and Wrangler's global options remain unsupported.

  • #​16739 6af492e Thanks @​GregBrimble! - Add custom Cloudflare API headers through CLOUDFLARE_API_HEADERS

    Set CLOUDFLARE_API_HEADERS to a JSON object such as {"X-Custom-Header":"value"} to add headers to Cloudflare API requests. Custom headers override existing unprotected request headers, body and transport headers are protected, and header values outside the diagnostic allowlist remain redacted regardless of log sanitization settings.

Patch Changes
  • #​16810 cdc970b Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-10

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

  • #​16810 cdc970b Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261109.1 ^5.20261110.1
    workerd 1.20261109.1 1.20261110.1
  • #​16709 022ee9d Thanks @​petebacondarwin! - Keep local Container images available for upload retries

    Keep prebuilt local image tags available until the caller finishes uploading the Worker and deploying its Container applications, so a later failure can be retried without rebuilding. When image push commands request cleanup, remove the source tag only after the push succeeds.

  • #​16740 44b39b0 Thanks @​GregBrimble! - Redact header values outside a safe diagnostic allowlist, regardless of log sanitization settings.

    Apply the same filtering to request, response, and request-options diagnostics. Strip X-Auth-Key alongside Authorization when forwarding local artifact Git requests.

  • #​16758 325dc69 Thanks @​petebacondarwin! - Fix JavaScript configuration parsing for Svelte projects using object spread

    Use a parser that supports object spread when updating JavaScript configuration files. This prevents configuration failures for Svelte projects using Drizzle or Better Auth and other framework configurations containing modern JavaScript syntax.

    Vite autoconfiguration reports a configuration error when an object spread, computed property, or accessor after the plugins array could override the Cloudflare plugin. Place the effective plugins array after these properties before retrying autoconfiguration.

  • Updated dependencies [cdc970b, cdc970b, 4e7e9f1, 267dadb, 44b39b0]:


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 CLI.

@tbhb-dev-renovate
tbhb-dev-renovate Bot enabled auto-merge (squash) November 16, 2026 06:55
@tbhb-dev-renovate
tbhb-dev-renovate Bot force-pushed the renovate/vitest-playwright-and-workerd branch 4 times, most recently from 4d606d7 to e8b77cc Compare November 19, 2026 01:25
Signed-off-by: tbhb-dev-renovate[bot] <289255489+tbhb-dev-renovate[bot]@users.noreply.github.com>
@tbhb-dev-renovate
tbhb-dev-renovate Bot force-pushed the renovate/vitest-playwright-and-workerd branch from e8b77cc to 2b4989b Compare November 19, 2026 09:00
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.

0 participants