Repository navigation
fix(deps): update non-major - #1394
Open
renovate[bot] wants to merge 2 commits into
Open
renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
Coverage Report
File CoverageNo changed files found. |
Contributor
📚 TypeDoc Generation Result✅ TypeDoc generated successfully!
The TypeDoc JSON file has been generated and validated. All documentation scripts completed successfully. |
renovate
Bot
force-pushed
the
renovate/non-major
branch
5 times, most recently
from
November 4, 2026 07:35
5f4df5c to
72c3648
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/non-major
branch
10 times, most recently
from
November 9, 2026 20:59
b623a73 to
8c21195
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 10, 2026 13:03
3a12a79 to
6064fe0
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 10, 2026 23:54
53373a8 to
12ab06f
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 11, 2026 16:38
2911420 to
88d1494
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 12, 2026 17:05
9322a29 to
ca3145f
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 13, 2026 22:00
4f5a2dc to
e86807c
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 15, 2026 00:09
7846e02 to
0b92eae
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 16, 2026 16:24
ead4e41 to
b6d1bd4
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 17, 2026 10:43
612f475 to
6cf3be4
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 17, 2026 10:45
340cb5b to
c24f6ea
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 17, 2026 23:11
c5f590b to
48f10f6
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 18, 2026 15:06
33e99e8 to
f613d5a
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 19, 2026 11:22
213ebc2 to
6715eb3
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 19, 2026 21:51
d3b4696 to
2a64603
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 20, 2026 07:34
64e64a2 to
2579dc6
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 21, 2026 01:57
8dfef91 to
92640ce
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 21, 2026 14:56
d94956b to
f4b7807
Compare
renovate
Bot
force-pushed
the
renovate/non-major
branch
from
November 21, 2026 23:16
6fa2a4a to
de478f5
Compare
This branch has not been deployed
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^1.4.10→^1.9.048f2562→c5e23b78f86cfb→74c2d92^5.1.4→^5.1.5^6.43.0→^6.47.0^0.75.0→^0.79.0^1.90.0→^1.94.0^7.0.2005→^7.0.20077.0.20085f6978f→3ffccac^0.0.92→^0.0.94^1.64.1→^1.65.1^1.2.15→^1.3.3^7.30.1→^7.30.2Release Notes
cloudflare/workers-sdk (@cloudflare/vitest-plugin)
v1.9.0Compare Source
Minor Changes
#16174
629f135Thanks @james-elicx! - Remove the dependency onwranglerThe Vitest plugin no longer depends on
wrangler. Reading the Wrangler configuration file, generating Miniflare options, loading local variables and serving the PagesASSETSbinding now use shared workers-sdk packages that are bundled into the plugin. Installing the plugin no longer installswrangleras well. If your project runs thewranglerCLI (for examplewrangler types), addwranglerto your owndevDependencies.Patch Changes
#17031
95fd4c2Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-19Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#17043
4f5b118Thanks @petebacondarwin! - Update Undici to 7.30.2 to include upstream security fixesThis 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
1b563dbThanks @petebacondarwin! - Fix remote bindings authentication with API tokens scoped to an individual WorkerRemote 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
getPlatformProxyand 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.5Compare Source
Patch Changes
#17003
3595295Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-18Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16949
110c162Thanks @edmundhung! - Fail remote RPC binding requests on network errors instead of hangingRemote 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
6750663Thanks @penalosa! - FixDynamic requireerrors when importing packages from ES modulesImporting these packages in a Node.js ES module could fail with
Dynamic require of "..." is not supportedwhen 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.4Compare Source
Patch Changes
#16974
77b5ca7Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-17Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
77b5ca7,77b5ca7,51064e6,5f05841]:v1.8.3Compare Source
Patch Changes
#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
b219078,d36b39d,db3c071,81e56dd,e97c9f8,e97c9f8,349fc4e,0bf81ac,4335eac,d36b39d]: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]:v1.6.1Compare Source
Patch Changes
#16793
fea323aThanks @vicb! - Bumpcapnp-esto 0.0.17This release fixes 3 issues. See the release notes for details.
#16683
6f29f97Thanks @jamesopstad! - Stop persisting account selections made bycfand the Cloudflare Vite and Vitest pluginsProfiles 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,
cfand the Vite and Vitest plugins reuse the selection while running but ask again the next time they start. ConfigureaccountIdincloudflare.config.tsor set theCLOUDFLARE_ACCOUNT_IDenvironment variable to avoid repeated prompts.Wrangler's existing persistent account selection remains unchanged.
#16648
56459a5Thanks @dario-piotrowicz! - Update bundled third-party dependencies with known security fixesLocal 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
abf924eThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-06Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16792
de10016Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-09Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#15693
307a69aThanks @ghostwriternr! - Dispose Miniflare when a Vitest runtime fails to startPreviously, 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
cd24b27Thanks @matingathani! - Fixvi.mock()factories failing under Vitest 5.1Mock 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 withasyncLocalStorage.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.0Compare Source
Minor Changes
#16186
f1d81a2Thanks @leostera! - Support local Artifacts across Wrangler, Vite, and Workers VitestSet
remote: falseon an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omittedremotecontinues to use the deployed resource, with a warning that changes affect real repositories;remote: trueexplicitly selects it. When remote bindings are disabled (wrangler dev --local, or Vite'sremoteBindings: false), Artifacts bindings use the local simulator. Workers Vitest uses the local simulator whenremoteis omitted, so tests do not change real repositories by accident; setremote: trueto 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: truewith 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
dc35efbThanks @cjol! - Bump bundledbrace-expansionto pick up security fixesThese packages bundle
brace-expansion(a dependency ofminimatch), and the bundled versions were affected by published advisories. The bundles now includebrace-expansion2.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
dc35efbThanks @cjol! - Bump bundleddevaluefrom 5.6.3 to 5.9.3 to pick up security fixesdevalueis 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
dc35efbThanks @cjol! - Bump bundledminimatchfrom 5.1.6 to 5.1.9 to pick up security fixesThese 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'smigrations_patternrelies on.#16695
b2061f4Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-04Use 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.1Compare Source
Patch Changes
#16670
b14b9dcThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-03Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16609
da26b7fThanks @gpanders! - Fix tests failing to start withresolve.preserveSymlinksin isolatednode_moduleslayoutsWith
resolve.preserveSymlinks: truein a pnpm project, tests failed to start withNo 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 insidenode_modulesnow load from their real paths, and other files keep their symlinked paths.Updated dependencies [
b14b9dc,44d1ee4,b14b9dc,d2eda1c,2750917,34f34b3]:v1.5.0Compare Source
Minor Changes
#16424
1598fd3Thanks @edmundhung! - Promoteexperimental.newConfigto a stableconfigoptionThe experimental
experimental.newConfigoption is now the stableconfigoption. Passconfig: truetocloudflareTest()to load your Worker's bindings, entrypoint and compatibility settings fromcloudflare.config.tsin the project root, or pass the path of acloudflare.config.tselsewhere:configcan't be combined withwrangler.miniflareoptions are merged over the Worker fromcloudflare.config.ts, withminiflarevalues taking precedence. Config functions receive Vitest's mode asctx.mode, which defaults totestand can be changed with--mode.If you're moving from
experimental.newConfig, secrets are now read from Vite'senvDirinstead of the directory containingcloudflare.config.ts, and remote bindings authenticate withcfinstead of Wrangler.Patch Changes
#16642
d38cb02Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-02Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16623
51bbf8bThanks @petebacondarwin! - Deprecate shared tooling helper exports from MiniflareMiniflare continues to export
getNodeCompat,NodeJSCompatMode, andgetFreshSourceMapSupportfor 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: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.12Compare Source
Patch Changes
#16635
76e18a8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-01Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [
effe4ed,76e18a8,76e18a8,009ca6e,5740867,d174de8,aece4df,2667a9f,ed7fb41,f9dbb22]:v1.4.11Compare Source
Patch Changes
#15565
142230dThanks @luccamordente! - Flushconsole.log()calls made from another I/O context without waiting for the runner's next messageVitest 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 throughSELF, a queue consumer, awaitUntil()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://rConfiguration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate using a curated preset maintained by
. View repository job log here