Repository navigation
fix(deps): update vitest, playwright and workerd - #302
Open
tbhb-dev-renovate[bot] wants to merge 1 commit into
Open
tbhb-dev-renovate[bot] wants to merge 1 commit into
tbhb-dev-renovate[bot] wants to merge 1 commit into
Conversation
tbhb-dev-renovate
Bot
force-pushed
the
renovate/vitest-playwright-and-workerd
branch
4 times, most recently
from
November 19, 2026 01:25
4d606d7 to
e8b77cc
Compare
Signed-off-by: tbhb-dev-renovate[bot] <289255489+tbhb-dev-renovate[bot]@users.noreply.github.com>
tbhb-dev-renovate
Bot
force-pushed
the
renovate/vitest-playwright-and-workerd
branch
from
November 19, 2026 09:00
e8b77cc to
2b4989b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.6.1→1.8.21.65.0→1.65.11.65.0→1.65.14.159.0→4.162.0Move 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_testin playwright/e2e/smoke and//tests:versions_testin 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 bothworker-configuration.d.tsfiles. Until then bothworker_types_testtargets fail, as expected.Release Notes
cloudflare/workers-sdk (@cloudflare/vitest-plugin)
v1.8.2Compare Source
Patch Changes
#16849
3cea40bThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-12Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16886
63eb6daThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-13Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
f005593,61eacca,856842e,856842e,3cea40b,63eb6da,3cea40b,63eb6da,3b1b408,c889551,032f8c2,032f8c2]:v1.8.1Compare Source
Patch Changes
#16833
5f539b5Thanks @jamesopstad! - Namecfcommands and settings in remote bindings errorsWhen remote bindings could not authenticate, the error told you to run
wrangler whoami,wrangler logoutandwrangler login. It now namescf auth whoami,cf auth logoutandcf auth login. When a Flagship binding without anidneeded to run remotely, the error named Wrangler'sapp_idsetting and suggestedwrangler flagship apps create. It now namesidand suggestscf 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
8e57331Thanks @edmundhung! - Fix test files never finishing when a socket read rejects after a Worker handler has answeredPreviously, 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 runwaiting forever after the tests passed. Vitest now reports the unhandled error and the run ends.Updated dependencies [
8b2a363,5f539b5,dc47e6d,575d136,3626ee8]:v1.8.0Compare Source
Minor Changes
#16682
5966749Thanks @ghostwriternr! - Run the Containers thatcloudflare.config.tsattaches to Durable ObjectsPreviously, projects that load
cloudflare.config.tsthrough theconfigoption 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 containscloudflare.config.ts.cloudflare.config.tshas 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
877b249Thanks @jamesopstad! - Move streaming tail consumers toexperimental.streamingTailConsumersincloudflare.config.tsStreaming Tail Workers are now declared in a separate, experimental list instead of with
streaming: trueon atailConsumersentry.tailConsumersnow only lists Tail Workers with atail()handler. This is a breaking change to the experimental config API: move each entry that setstreaming: truetoexperimental.streamingTailConsumers, without thestreamingfield.Fields under
experimentalmay change or be removed without a major version bump. Thewrangler-to-cfcodemod now convertsstreaming_tail_consumerstoexperimental.streamingTailConsumers.#16734
c47cca7Thanks @matingathani! - Fix CommonJS dependencies being loaded as ES modules under Vitest 5 inline projectsA dependency with its own
"type": "commonjs"package.jsonwas treated as an ES module when an earlier.jsfile elsewhere in the project had been classified by the project's"type": "module"package.json. The dependency then failed at import with errors such asCannot set properties of undefinedorexports is not defined. The nearestpackage.jsonnow always decides how a.jsfile is loaded.Updated dependencies [
877b249,69e650c]:v1.7.0Compare Source
Minor Changes
#15695
d437be3Thanks @ghostwriternr! - Run the Containers that the Wrangler configuration attaches to Durable ObjectsPreviously, 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 realctx.container, so these projects now need Docker. To keep running their tests without Docker, setdev.enable_containerstofalsein the Wrangler configuration, which disables the Containers. Cloudflare-managed registry images are not supported yet.Patch Changes
#16810
cdc970bThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-10Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
cb9534f,6af492e,cdc970b,cdc970b,4e7e9f1,267dadb,022ee9d,44b39b0,325dc69]:microsoft/playwright (playwright)
v1.65.1Compare Source
Bug Fixes
Browser Versions
cloudflare/workers-sdk (wrangler)
v4.162.0Compare Source
Minor Changes
#16735
f005593Thanks @leostera! - Use the local simulator for Artifacts bindings that omitremoteBehavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted
remotein Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos inwrangler devorvite dev, set"remote": trueon the binding (dev: { remote: true }incloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.While
remoteis 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. Setremote: trueto use deployed repos, orremote: falseto silence this warning." Workers Vitest andwrangler dev --localalready 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
032f8c2Thanks @vaishnav-mk! - Reject settings on aworkflowsbinding to a Workflow declared inexportsA
workflowsbinding can still bind a Workflow that the Worker declares inexports, but it can no longer setlimits,concurrency,schedules,default_retention, orjurisdictionfor 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
032f8c2Thanks @vaishnav-mk! - Upload Workflow export settings with the Workerwrangler deployandwrangler versions uploadnow include the settings of eachworkflowexport (limits,concurrency,schedules,default_retention, andjurisdiction) in the upload, instead of sending only its type and name. Uploads of a Worker withworkflowexports also send aCloudflare-Workers-Script-Api-Dateheader, which lets the Workers API provision Workflow exports from these settings as part of the upload.wrangler deployandwrangler triggers deploystill 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 deploynow explains that scheduled Workflows require a paid Workers plan.Patch Changes
#16849
3cea40bThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-12Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16886
63eb6daThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-13Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16849
3cea40bThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16886
63eb6daThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16864
3b1b408Thanks @MattieTK! - Fix packages with nestedpackage.jsonfiles missing from deploy metadataPackages such as
hono,stripeand@modelcontextprotocol/sdkwere silently omitted from the package dependency metadata reported duringwrangler deployandwrangler versions upload. These packages are now included with their installed versions. Autoconfig and codemods also detect their installed versions correctly.#16862
c889551Thanks @petebacondarwin! - Fix requests hanging when a local Worker reload finishes before an inflight request failsWrangler 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.0Compare Source
Minor Changes
#16840
8b2a363Thanks @jamesopstad! - Write source maps in Build Output withsourcesrelative to each source map fileThis changes the experimental Build Output that
wrangler build --experimental-cf-build-outputandcf-wrangler buildwrite. Their source maps were prepared as if for upload, withsourcesrelative 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 inbundle/to the original files, like the source maps the Vite plugin writes.Patch Changes
#16833
5f539b5Thanks @jamesopstad! - Namecfcommands andcloudflare.config.tssettings in remote bindings errors fromcf-wranglerWhen
cfruns development through thecf-wranglerdelegate and remote bindings cannot be authenticated, the error now tells you to runcf auth whoami,cf auth logoutandcf auth logininstead 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'sidsetting instead ofapp_id, and suggestscf flagship apps create.wrangler devstill names Wrangler's commands and settings.#16527
dc47e6dThanks @petebacondarwin! - Normalize relative redirect pathnames consistently across Pages and Workers assetsRelative
_redirectstargets 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
575d136Thanks @edmundhung! - Update@netlify/build-infoto 11.3.1#16838
3626ee8Thanks @jamesopstad! - Keep the remote bindings session when you remove the last remote bindingWhen you removed the last remote binding while
wrangler devwas running, Wrangler restarted the remote bindings session with credentials that ignored--profileand theaccount_idin 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.1Compare Source
Patch Changes
877b249,69e650c]:v4.160.0Compare Source
Minor Changes
#16760
cb9534fThanks @petebacondarwin! - Support forwarded Wrangler development server options in the experimentalcf-wranglerdelegatecf devcan now forward options such as--inspector-port 9229,--ip,--var, and--persist-toto the Wrangler development runtime. The delegate reuses Wrangler's dev option definitions and validation while retaining project config discovery,--modeenvironment selection, local development, and its.cloudflare/statedefault. 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 examplecf dev -- --local --persist-to "custom state". Config and script overrides, whole-worker remote development, and Wrangler's global options remain unsupported.#16739
6af492eThanks @GregBrimble! - Add custom Cloudflare API headers throughCLOUDFLARE_API_HEADERSSet
CLOUDFLARE_API_HEADERSto 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
cdc970bThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-10Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16810
cdc970bThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16709
022ee9dThanks @petebacondarwin! - Keep local Container images available for upload retriesKeep 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
44b39b0Thanks @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-KeyalongsideAuthorizationwhen forwarding local artifact Git requests.#16758
325dc69Thanks @petebacondarwin! - Fix JavaScript configuration parsing for Svelte projects using object spreadUse 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)
🚦 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.
This PR has been generated by Mend Renovate CLI.