Repository navigation
fix(deps): update all non-major dependencies - #193
Open
khepri-bot[bot] wants to merge 1 commit into
Open
khepri-bot[bot] wants to merge 1 commit into
khepri-bot[bot] wants to merge 1 commit into
Conversation
khepri-bot
Bot
force-pushed
the
renovate/all-non-major-dependencies
branch
8 times, most recently
from
November 19, 2026 20:46
f8bb047 to
6c837f2
Compare
khepri-bot
Bot
force-pushed
the
renovate/all-non-major-dependencies
branch
from
November 20, 2026 20:31
6c837f2 to
c10a02c
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.65.0→1.67.01.70.1(+4)1.4.8→1.6.01.9.0(+8)1.64.1→1.65.01.65.111.9.0→11.11.011.16.0(+4)11.9.0→11.11.011.16.0(+4)1.0.0→1.0.12.0.1(+3)4.3.3→4.3.526.6.5→26.6.66.2.6→6.2.76.2.8v26.12.1→26.13.0v26.13.126.12.1→26.13.026.13.112.16.0→12.18.012.21.0(+2)v6.1.0→v6.1.17.1.1→7.1.27.1.31.9.17→1.9.182.0.3(+5)4.3.3→4.3.58.3.5→8.3.68.3.8(+1)2.11.14→2.11.152.11.17(+1)5.0.5→5.1.05.1.14.153.0→4.158.04.166.0(+8)8.22.0→8.22.18.23.0(+1)Release Notes
cloudflare/workers-sdk (@cloudflare/vite-plugin)
v1.67.0Compare Source
Minor Changes
#16543
0489cdaThanks @petebacondarwin! - Validate asset ignore files and update local Flagship supportUpgrade Miniflare to 5.20261023.2-beta and Wrangler to 4.155.0. Builds and asset manifest generation now reject
.assetsignorefiles with invalid UTF-8 or null characters instead of silently ignoring their patterns. The Local Explorer also supports Flagship management by app ID, and local flag evaluations retain metadata.Miniflare also waits for temporary file cleanup before disposal completes, so closing or restarting a Vite dev server finishes cleanup before returning.
#16579
e696113Thanks @petebacondarwin! - Support remote Analytics Engine bindings in Vite plugin v1Set
remote: trueon ananalytics_engine_datasetsentry inwrangler.jsoncto sendwriteDataPoint()calls from local development and preview to the real dataset.Patch Changes
#16578
2eae147Thanks @petebacondarwin! - Close Vite HMR WebSocket upgrades when Vite WebSockets are disabledPreviously,
server.ws: falseleft the browser's raw upgrade socket pending because no Vite handler claimed it. Worker and Sandbox WebSocket forwarding remains unchanged.#16639
a6f98d0Thanks @petebacondarwin! - Update the v1 local runtime to workerd 1.20261101.1Upgrade Miniflare to 5.20261101.0-beta with matching Wrangler and shared SDK dependencies. Local development and preview use the November 1 runtime, and Workers without an explicit compatibility date default to 2026-11-01. Update Workers types to match the runtime.
v1.66.0Compare Source
Minor Changes
#16539
046db08Thanks @petebacondarwin! - Update the development registry to use the canonical Cloudflare pathUpgrade Miniflare to 5.20261023.1-beta and Wrangler to 4.154.0. Vite plugin v1 now uses
CLOUDFLARE_DEV_REGISTRY_PATHor<Cloudflare config directory>/dev-registry/v5for Worker discovery.MINIFLARE_REGISTRY_PATHis no longer read. When mixing Vite and Wrangler development sessions, set the sameCLOUDFLARE_DEV_REGISTRY_PATHfor both because Wrangler retains its legacy default.#16407
9ec1101Thanks @petebacondarwin! - Support remote Hyperdrive bindings in Vite plugin v1 development and previewSet
remote: trueon a Hyperdrive binding inwrangler.jsoncto connect to its deployed configuration without a local database connection string. The retained remote proxy exposes the binding's connection string and socket streams, and remote session cleanup preserves startup errors and shares one disposal attempt.Patch Changes
#16542
ef573d4Thanks @petebacondarwin! - Preserve machine-readable error properties from remote bindingsEnable enhanced error serialization on the remote proxy Worker used by Vite plugin v1. Combined with Miniflare 5.20261023.1-beta, remote binding errors retain properties such as
codeandnumericCodeso Worker code can handle them without parsing error messages.#16480
ccaa34aThanks @petebacondarwin! - Prevent malformed token-exchange responses from crashing remote binding startupUpdate the Undici dependency bundled from the retained remote-bindings package to
7.30.1. Responses with excessive content encodings now reject without a later unhandled stream error when the server closes the connection early.#16502
6f2eda1Thanks @petebacondarwin! - Update the retained asset configuration validator to Zod 4.6.6The Vite plugin validates
_headersand_redirectsthrough its private workers-shared package. Update that bundled copy to address excessive memory consumption when validating oversized collections.#16444
79678c4Thanks @petebacondarwin! - Update Vite plugin v1 to the October 23 Workers runtimeUse Miniflare
5.20261023.0-betaand the matching Wrangler release for local development and preview. Align bundled helpers and Workers types with this runtime, and use2026-10-23as the fallback compatibility date when none is configured. The runtime and helper updates also prevent malformed HTTP responses with excessive content encodings from causing unhandled stream errors. The published helpers also update their bundled Zod validator and fix Windows keyring setup for remote-binding credentials when the configuration path contains spaces.#16479
1d5354bThanks @petebacondarwin! - Treatcloudflare:durable-objectsas a built-in runtime moduleWorkers can import
retryable()fromcloudflare:durable-objectsto mark Durable Object methods as safe to retry. The plugin now leaves that import for the runtime to resolve, as it does forcloudflare:workers, instead of trying to resolve it as a package.#16493
4ce6176Thanks @petebacondarwin! - Preserve a Worker response'sstatusTextin Vite dev and previewResponses such as
new Response(body, { status: 231, statusText: "Custom" })now reach the browser as231 Custominstead of231 unknown. Empty status text is also preserved over HTTP/1.x.#16501
109844eThanks @petebacondarwin! - Preserve separateSet-Cookierequest headers in Vite dev and previewWorkers now receive each incoming
Set-Cookievalue separately for HTTP requests and WebSocket upgrades, including values with commas in anExpiresdate. Previously, multiple values could be combined into one header.#16503
ca116f9Thanks @petebacondarwin! - Fix a dev server failing to start when an earlier dev server in the same process had different Worker exportsThe Vite plugin now clears the Worker export types it detected when a dev server closes. A dev server created afterwards in the same process derives them from its own config again, so it no longer fails with
Class extends value undefinedfor a Durable Object the earlier server's Worker did not export.#16504
436fa9aThanks @petebacondarwin! - Fix Vite DevTools WebSocket connections closing unexpectedlyLeave upgrades at
/__devtools/__wsto Vite DevTools instead of forwarding them to the Worker. Sandbox preview requests continue to reach the Worker.cloudflare/workers-sdk (@cloudflare/vitest-plugin)
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
8b64becThanks @swalker326! - Fix Durable Object self-references in tests and container validationDurable Object bindings that explicitly name the Worker itself now resolve to the test runner in
@cloudflare/vitest-plugin, for bothcloudflare.config.tsand Wrangler configuration files. Named Wrangler environments use their effective Worker name, keeping bindings to the base Worker external. Container validation also accepts these self-references, using the effective deployment name to distinguish local and external bindings.Explicit binding targets remain intact during configuration conversion, so deploying with
--nameor a CI name override preserves the intended Durable Object target.Updated dependencies [
ec0bea4,b4653b4,25802bc,25802bc,15fbaed,d8899ac,8b64bec]:v1.4.10Compare Source
Patch Changes
a95d647,c7a3373,c7a3373,c7a3373,c7a3373,c7a3373]:v1.4.9Compare Source
Patch Changes
0968b08,f3c13b3]:microsoft/playwright (@playwright/test)
v1.65.0Compare Source
🥟 Run tests with Bun
The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the
--bunflag, because without itbunx playwright testruns on Node.js:bunx --bun playwright testOur CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:
--only-changeddoes not follow imports.--tsconfigand the JSX options intsconfig.jsonhave no effect, and custom ESM loaders are not supported.clickinstead oflocator.click. This changes some step locations, step titles and error messages.🚨 Reports with only failures
New
failuresreporter prints failures and successful retries as they occur, followed by a summary, without progress output.New
onlyFailuresoption of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:🎯 Test runner
New built-in
-exclusive-test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:
New
PLAYWRIGHT_TRANSFORM_CACHE_DIRenvironment variable sets the directory for transpiled test files, for example on a Linux machine shared with other users.New APIs
timeoutandsignalin cdpSession.send().Notable Changes⚠️
TypeScript class fields now follow
useDefineForClassFieldsfrom yourtsconfig.json, the same astsc. It is enabled forES2022and later targets, and whentargetis not specified. A field initializer that reads a constructor parameter property now fails, because the initializer runs first:Move the initialization to the constructor, or set
"useDefineForClassFields": falsein yourtsconfig.json.Actions such as locator.click(), locator.check(), locator.tap(), locator.fill(), locator.clear() and locator.selectOption() now wait for the element to be not inert. An action on an element with the
inertattribute, or inside such an element, now times out if the element stays inert.A sharded run now fails with "No tests found" when no tests match across all shards. Pass
--pass-with-no-teststo allow this. An empty shard still passes when other shards have tests.Cookie matching now follows RFC 6265. With a URL, browserContext.cookies() and apiRequestContext.cookies() no longer return host-only cookies for subdomains or
Path=/apicookies for/apiv2, and aPath=/foo/cookie does not match/foo. APIRequestContext sends a cookie without a name asCookie: xinstead ofCookie: =x, and storesSet-Cookie: tokenas a cookie without a name.Proxy credentials are no longer sent to websites. The credentials in the
proxyoption now answer only proxy challenges. To authenticate on a website, usehttpCredentials.Text that the browser does not render, such as text that is not assigned to a slot or text directly inside a closed
<details>, is no longer part of accessible names and aria snapshots. This can change the results of page.getByRole() with a name, locator.ariaSnapshot() and expect(locator).toMatchAriaSnapshot().String and
URLSearchParamsvalues of theparamsoption in APIRequestContext requests are now appended to the query that the URL already has, instead of replacing it..css,.lessand.scssimports in test files now load as empty modules instead of being removed, so the imported file must exist.The blob reporter again deletes the content of its output directory before it writes the report. Playwright 1.64 kept reports with other names.
Test locations of imported calls such as
test(in CommonJS output now point to the start of the callee, for examplea.spec.ts:3:7instead ofa.spec.ts:3:11. This is the same as in ESM.Announcements
Browser Versions
This version was also tested against the following stable channels:
getsentry/sentry-javascript (@sentry/cloudflare)
v11.11.0Compare Source
Important Changes
ref(cloudflare): Use the shared request handler wrapper (#25588)
Cloudflare Workers now use the same request handler wrapper as
Deno.serveandBun.serve. Changes for Cloudflare users:client.addressfrom theCF-Connecting-IPheader (or another forwarding header), as on the other runtimes. This followsdataCollection.userInfo, which istrueby default. To leave it out, setdataCollection: { userInfo: false }.responsecontext with the status code.captureErrors: false, it does not capture it.Set-Cookieheader of a response, as on Deno and Bun.AsyncLocalStorage(for example on Shopify Oxygen), events now also get the request URL and method.feat(nestjs): Add an option to monitor every @Cron method (#25471)
Set
monitorCronJobs: trueonnestIntegration()to send check-ins for every@Cron()method, without adding@SentryCronto each one. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. UseexcludeCronJobsto skip jobs by slug. Methods that also have@SentryCroncheck in once, with the slug and options passed to@SentryCron.feat(node): Add cronJobIntegration to monitor cron jobs (#25477)
Add
Sentry.cronJobIntegration()tointegrationsto send check-ins for every namedCronJobof thecronpackage (4.3+), with the job name as the monitor slug. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. UseexcludeJobsto skip jobs by name.Sentry.cron.instrumentCronis deprecated; usecronJobIntegrationinstead.fix(server-utils): Instrument @anthropic-ai/sdk 1.x and turn off its own OTel spans (#25750)
The Anthropic integration now instruments
@anthropic-ai/sdk1.x. Since 0.134 the SDK also records its own OpenTelemetry spans, such asanthropic.messages.create, which duplicated Sentry'sgen_aispans. Once Sentry instruments the SDK, it setsANTHROPIC_OPEN_TELEMETRY=falseto turn those spans off. To keep them, setANTHROPIC_OPEN_TELEMETRY=trueor pass theopenTelemetryoption to the Anthropic client.feat(nextjs): Mark pageloads of cached pages (#25318)
When Next.js serves a page from its cache, for example an ISR page or a
cacheComponentsshell, the pageload now has thepage.server_rendering.typeattribute. It isstaticif the whole page came from the cache, andpartially_staticif parts of it rendered for this request. Then the pageload stays connected to this request, as before. If the request that rendered the cached page was sampled, the pageload also links to it. So in Sentry, a cached page no longer looks like missing server instrumentation.Other Changes
@sentry/astro/integrationentry for the Astro integration (#25726)sourcemaps.deleteSourcemapsAfterUploadand staged uploads (#25637)applicationKeyExcludeDependenciesoption (#25818)awsLambdaWebIntegrationfor Lambda Web Functions (#25355)getSqlSpanNamefor SQL span names (#25929)getSqlQueryAttributeshelper for consistency (#25927)db.operation.nameon SQL spans (#25850)withSentryfrom@sentry/solidstart/vite(#25725)handleTunnelRequestform and reword theserveTunnelIntegrationdocs (#25844)Internal Changes
Configuration
📅 Schedule: (in timezone America/New_York)
* 0-8 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.