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
3 times, most recently
from
November 17, 2026 04:04
89d2c65 to
734a257
Compare
khepri-bot
Bot
force-pushed
the
renovate/all-non-major-dependencies
branch
from
November 17, 2026 16:12
2009db3 to
3255bf4
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.0(+3)1.4.8→1.5.11.8.4(+7)11.9.0→11.10.011.14.0(+3)11.9.0→11.10.011.14.0(+3)1.0.0→1.0.12.0.0(+2)4.3.3→4.3.44.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.17.012.21.0(+3)v6.1.0→v6.1.11.9.17→1.9.182.0.1(+2)4.3.3→4.3.44.3.52.11.14→2.11.152.11.165.0.5→5.1.05.1.14.153.0→4.157.04.164.0(+7)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.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]:getsentry/sentry-javascript (@sentry/cloudflare)
v11.10.0Compare Source
Important Changes
feat: Add a managed tunnel that the SDK derives from the DSN (#25199, #25200, #25783)
Set
tunnel: truein your browserSentry.initcall to send events through your own server. This helps when ad blockers block requests to Sentry. The browser derives the tunnel path from the DSN, so older and newer builds of your client and server always agree on the path.To serve the tunnel, add
serveTunnelIntegration()to your server SDK. Astro, Nuxt, Nitro, React Router, Remix 3, SolidStart, SvelteKit and TanStack Start then answer tunnel requests automatically:If the browser uses a different DSN than the server, set
serveTunnelIntegration({ allowedDsns: [browserDsn] }). For other setups, the server SDKs exporthandleTunnelRequestIfMatched,handleTunnelRequest,isTunnelRequestandgetTunnelPath:The
requestoption ofhandleTunnelRequestis deprecated and will be removed in v12.feat: Make span origins spec compliant (#25602)
Some span origins changed their names to follow the trace origin spec:
auto.amqplib.*is nowauto.queue.amqplib.*, andauto.kafkajs.*is nowauto.queue.kafkajs.*.auto.vercelai.channelis nowauto.ai.vercelai.auto.firebase.firestoreis nowauto.db.firebase.firestore, andauto.firebase.functionsis nowauto.function.firebase.auto.aws.aws_sdkis nowauto.{rpc,db,queue,ai}.aws_sdk, with the category from the span op.auto.aws_lambdais nowauto.function.aws_serverless.auto.mcp.notificationis nowauto.function.mcp_server.notification.auto.db.cloudflare.durable_object.sqlis nowauto.db.cloudflare.durable_object_sql.auto.http.browser.{lcp,cls,inp}is nowauto.ui.browser.{lcp,cls,inp}.If you have
ignoreSpansrules, queries or alerts on the old origins, change them to use the new origins.feat(bun): Add incoming request options and request sessions to
bunServerIntegration(#25580)bunServerIntegrationnow accepts the same options asdenoServeIntegration:ignoreRequestBody,ignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreated,onSpanEnd,sessionsandsessionFlushingDelayMS. The callbacks receive the webRequest.Bun.servenow records a request session for each incoming request. Sessions are sent only when areleaseis set. To turn them off, setbunServerIntegration({ sessions: false }).ignoreStaticAssetsdefaults totrue, soBun.serveno longer creates spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, setbunServerIntegration({ ignoreStaticAssets: false }).Bun.servespans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown forOPTIONSandHEADrequests are now captured.feat(bun): Inject debug IDs and upload source maps in
sentryBunPlugin(#25670)sentryBunPluginfrom@sentry/bun/pluginnow accepts the same options assentryEsbuildPlugin(org,project,authToken,release,sourcemaps, ...). WhenBun.buildwrites source maps tooutdir, the plugin injects the debug ID that Bun writes into each bundle, injects the release, and uploads the source maps at the end of the build. You no longer need to runsentry sourcemap injectandsentry sourcemap uploadafter the build.Like the other bundler plugins,
sentryBunPluginnow sends build telemetry and injects the release it detects (for example, from git). To turn off telemetry, settelemetry: false.feat(cloudflare): Add incoming request span options to
httpServerIntegration(#25582)Cloudflare's
httpServerIntegrationnow acceptsignoreIncomingRequests,ignoreStaticAssets,spans,onSpanCreatedandonSpanEnd, with the same meaning as in the Node, Deno and Bun integrations. The callbacks receive the webRequest.ignoreStaticAssetsdefaults totrue, so workers no longer create spans forGETrequests to common static assets such asfavicon.ico,robots.txtor*.jsfiles. To keep these spans, sethttpServerIntegration({ ignoreStaticAssets: false }). Request spans also follow the client's tracing configuration by default, so the SDK does not start them when tracing is disabled. IfignoreRequestBodythrows, the request no longer fails, and the SDK skips the body.feat(cloudflare): Let users configure the channel integrations (#25584)
When the
@sentry/cloudflare/viteplugin bundles an instrumented package (for examplepgoropenai), the SDK adds the matching integration with its default options.@sentry/cloudflarenow exports these integrations, so you can set their options, for example ininstrument.server.ts:These integrations need the vite plugin. Without it, they record nothing, and with
debug: truethe SDK logs a warning.feat(node): Add
onSpanEndtohttpIntegration(#25581)httpIntegrationandhttpServerSpansIntegrationnow acceptonSpanEnd, a hook that runs when the response for an incoming request finishes, before its span ends. Use it to change the span based on the response. Deno and Bun already have this option.feat(node, bun, deno, cloudflare): Align portable exports across server SDKs (#25583)
Node, Bun, Deno and Cloudflare now export the same helpers from
@sentry/coreand@sentry/server-utilswhere they work on that runtime:moduleMetadataIntegration,instrumentPostgresJsSql,instrumentCreateReactAgent,awsIntegrationand theFlueOptionstype.awsIntegrationwas already in their default integrations.parameterizeandinstrumentStateGraphCompile.LogandLogSeverityLeveltypes.fastifyIntegration, which was already in its default integrations.feat(nuxt): Start the server SDK on the Nuxt Vite server (experimental) (#25524)
Sentry now supports Node.js production builds using Nuxt 4.6's experimental Vite server (
server: { builder: 'vite' }). Yoursentry.server.configloads automatically, enabling request tracing and automatic database spans for supported libraries.Development mode, Cloudflare, automatic capture of server rendering errors, and connecting server and browser traces via HTML meta tags are not yet supported. This experimental support may change in minor releases.
ref(deno, bun): Use a shared request handler wrapper for
Deno.serveandBun.serve(#25586, #25587)Deno.serveandBun.servenow use the same request handler wrapper, which Cloudflare will also use. On both runtimes, errors inOPTIONSandHEADrequests now carry the request data, and the SDK keeps everySet-Cookieheader of a response instead of only the last one.For Deno users:
Bun.servespans now follow the Sentry conventions forhttp.serverspans, as on Node, Deno and Cloudflare:url.templateis nowhttp.route. Routes without parameters also gethttp.routeand theroutesource.url.domainis nowserver.address./gets theroutesource and the nameGET /.user_agent.originalandhttp.request.body.size.Other Changes
execute_toolspans for Anthropic'sbeta.sessions.events.toolRunner()(#25554)varin the Vite transform (#25663)defaultkeyword in the Vite transform (#25741)undicifetch andnode:http(#25441)Internal Changes
ServerRequestOptionstype across runtimes (#25579)GEN_AI_EXTRACTop from@sentry/conventions(#25734)Work in this release was contributed by @4ktLuffy, @faizansaiyed123, @itisrmk, @kunal649, @kyrylolvov, @larcane97, @lfantone, @pcbeingused333, @psh4607, and @seongwon030. Thank you for your contributions!
solidjs/solid-router (@solidjs/router)
v1.0.1Patch Changes
eaafba6: Stamp history depth from the current entry instead ofhistory.length, souseBeforeLeaveand scroll restoration keep working on Back once the browser's session history is full (#694)c3cbd67: Throw a descriptive error in development when an action is called directly instead of throughuseAction.473c270: Anchor click handling no longer intercepts links with a non-http(s) scheme (blob:,mailto:,tel:,data:, …). Previouslyblob:links could be wrongly routed because they inherit the page origin and bypassed the same-origin check.5a46ba1: Speed up<A>server rendering by roughly 5x<A>spent most of its server render time inmergePropsandsplitProps, which buildaccessor-backed prop objects that can never be observed during a one shot
renderToString. The defaultactiveClass/ `inactivConfiguration
📅 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.