Skip to content

fix(deps): update all non-major dependencies - #193

Open
khepri-bot[bot] wants to merge 1 commit into
mainfrom
renovate/all-non-major-dependencies
Open

khepri-bot[bot] wants to merge 1 commit into
mainfrom
renovate/all-non-major-dependencies

Conversation

@khepri-bot

@khepri-bot khepri-bot Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@cloudflare/vite-plugin (source) 1.65.0 → 1.67.0 age confidence devDependencies minor 1.70.1 (+4)
@cloudflare/vitest-plugin (source) 1.4.8 → 1.6.0 age confidence devDependencies minor 1.9.0 (+8)
@playwright/test (source) 1.64.1 → 1.65.0 age confidence devDependencies minor 1.65.1
@sentry/cloudflare (source) 11.9.0 → 11.11.0 age confidence dependencies minor 11.16.0 (+4)
@sentry/solid (source) 11.9.0 → 11.11.0 age confidence dependencies minor 11.16.0 (+4)
@solidjs/router 1.0.0 → 1.0.1 age confidence dependencies patch 2.0.1 (+3)
@tailwindcss/vite (source) 4.3.3 → 4.3.5 age confidence devDependencies patch
@types/node (source) 26.6.5 → 26.6.6 age confidence devDependencies patch
fake-indexeddb 6.2.6 → 6.2.7 age confidence devDependencies patch 6.2.8
node (source) v26.12.1 → 26.13.0 age confidence engines minor v26.13.1
node 26.12.1 → 26.13.0 age confidence uses-with minor 26.13.1
pnpm (source) 12.16.0 → 12.18.0 age confidence packageManager minor 12.21.0 (+2)
pnpm/action-setup v6.1.0 → v6.1.1 age confidence action patch
rollup-plugin-visualizer 7.1.1 → 7.1.2 age confidence devDependencies patch 7.1.3
solid-js (source) 1.9.17 → 1.9.18 age confidence dependencies patch 2.0.3 (+5)
tailwindcss (source) 4.3.3 → 4.3.5 age confidence devDependencies patch
vite (source) 8.3.5 → 8.3.6 age confidence devDependencies patch 8.3.8 (+1)
vite-plugin-solid 2.11.14 → 2.11.15 age confidence devDependencies patch 2.11.17 (+1)
vitest (source) 5.0.5 → 5.1.0 age confidence devDependencies minor 5.1.1
wrangler (source) 4.153.0 → 4.158.0 age confidence devDependencies minor 4.166.0 (+8)
ws 8.22.0 → 8.22.1 age confidence dependencies patch 8.23.0 (+1)

Release Notes

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

v1.67.0

Compare Source

Minor Changes
  • #​16543 0489cda Thanks @​petebacondarwin! - Validate asset ignore files and update local Flagship support

    Upgrade Miniflare to 5.20261023.2-beta and Wrangler to 4.155.0. Builds and asset manifest generation now reject .assetsignore files 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 e696113 Thanks @​petebacondarwin! - Support remote Analytics Engine bindings in Vite plugin v1

    Set remote: true on an analytics_engine_datasets entry in wrangler.jsonc to send writeDataPoint() calls from local development and preview to the real dataset.

Patch Changes
  • #​16578 2eae147 Thanks @​petebacondarwin! - Close Vite HMR WebSocket upgrades when Vite WebSockets are disabled

    Previously, server.ws: false left the browser's raw upgrade socket pending because no Vite handler claimed it. Worker and Sandbox WebSocket forwarding remains unchanged.

  • #​16639 a6f98d0 Thanks @​petebacondarwin! - Update the v1 local runtime to workerd 1.20261101.1

    Upgrade 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.0

Compare Source

Minor Changes
  • #​16539 046db08 Thanks @​petebacondarwin! - Update the development registry to use the canonical Cloudflare path

    Upgrade Miniflare to 5.20261023.1-beta and Wrangler to 4.154.0. Vite plugin v1 now uses CLOUDFLARE_DEV_REGISTRY_PATH or <Cloudflare config directory>/dev-registry/v5 for Worker discovery. MINIFLARE_REGISTRY_PATH is no longer read. When mixing Vite and Wrangler development sessions, set the same CLOUDFLARE_DEV_REGISTRY_PATH for both because Wrangler retains its legacy default.

  • #​16407 9ec1101 Thanks @​petebacondarwin! - Support remote Hyperdrive bindings in Vite plugin v1 development and preview

    Set remote: true on a Hyperdrive binding in wrangler.jsonc to 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 ef573d4 Thanks @​petebacondarwin! - Preserve machine-readable error properties from remote bindings

    Enable 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 code and numericCode so Worker code can handle them without parsing error messages.

  • #​16480 ccaa34a Thanks @​petebacondarwin! - Prevent malformed token-exchange responses from crashing remote binding startup

    Update 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 6f2eda1 Thanks @​petebacondarwin! - Update the retained asset configuration validator to Zod 4.6.6

    The Vite plugin validates _headers and _redirects through its private workers-shared package. Update that bundled copy to address excessive memory consumption when validating oversized collections.

  • #​16444 79678c4 Thanks @​petebacondarwin! - Update Vite plugin v1 to the October 23 Workers runtime

    Use Miniflare 5.20261023.0-beta and the matching Wrangler release for local development and preview. Align bundled helpers and Workers types with this runtime, and use 2026-10-23 as 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 1d5354b Thanks @​petebacondarwin! - Treat cloudflare:durable-objects as a built-in runtime module

    Workers can import retryable() from cloudflare:durable-objects to mark Durable Object methods as safe to retry. The plugin now leaves that import for the runtime to resolve, as it does for cloudflare:workers, instead of trying to resolve it as a package.

  • #​16493 4ce6176 Thanks @​petebacondarwin! - Preserve a Worker response's statusText in Vite dev and preview

    Responses such as new Response(body, { status: 231, statusText: "Custom" }) now reach the browser as 231 Custom instead of 231 unknown. Empty status text is also preserved over HTTP/1.x.

  • #​16501 109844e Thanks @​petebacondarwin! - Preserve separate Set-Cookie request headers in Vite dev and preview

    Workers now receive each incoming Set-Cookie value separately for HTTP requests and WebSocket upgrades, including values with commas in an Expires date. Previously, multiple values could be combined into one header.

  • #​16503 ca116f9 Thanks @​petebacondarwin! - Fix a dev server failing to start when an earlier dev server in the same process had different Worker exports

    The 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 undefined for a Durable Object the earlier server's Worker did not export.

  • #​16504 436fa9a Thanks @​petebacondarwin! - Fix Vite DevTools WebSocket connections closing unexpectedly

    Leave upgrades at /__devtools/__ws to 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.0

Compare Source

Minor Changes
  • #​16186 f1d81a2 Thanks @​leostera! - Support local Artifacts across Wrangler, Vite, and Workers Vitest

    Set remote: false on an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omitted remote continues to use the deployed resource, with a warning that changes affect real repositories; remote: true explicitly selects it. When remote bindings are disabled (wrangler dev --local, or Vite's remoteBindings: false), Artifacts bindings use the local simulator. Workers Vitest uses the local simulator when remote is omitted, so tests do not change real repositories by accident; set remote: true to 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: true with 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 dc35efb Thanks @​cjol! - Bump bundled brace-expansion to pick up security fixes

    These packages bundle brace-expansion (a dependency of minimatch), and the bundled versions were affected by published advisories. The bundles now include brace-expansion 2.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 dc35efb Thanks @​cjol! - Bump bundled devalue from 5.6.3 to 5.9.3 to pick up security fixes

    devalue is 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 dc35efb Thanks @​cjol! - Bump bundled minimatch from 5.1.6 to 5.1.9 to pick up security fixes

    These 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's migrations_pattern relies on.

  • #​16695 b2061f4 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-04

    Use 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.1

Compare Source

Patch Changes
  • #​16670 b14b9dc Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-03

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

  • #​16609 da26b7f Thanks @​gpanders! - Fix tests failing to start with resolve.preserveSymlinks in isolated node_modules layouts

    With resolve.preserveSymlinks: true in a pnpm project, tests failed to start with No 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 inside node_modules now load from their real paths, and other files keep their symlinked paths.

  • Updated dependencies [b14b9dc, 44d1ee4, b14b9dc, d2eda1c, 2750917, 34f34b3]:

v1.5.0

Compare Source

Minor Changes
  • #​16424 1598fd3 Thanks @​edmundhung! - Promote experimental.newConfig to a stable config option

    The experimental experimental.newConfig option is now the stable config option. Pass config: true to cloudflareTest() to load your Worker's bindings, entrypoint and compatibility settings from cloudflare.config.ts in the project root, or pass the path of a cloudflare.config.ts elsewhere:

    cloudflareTest({ config: true });
    cloudflareTest({ config: "./worker/cloudflare.config.ts" });

    config can't be combined with wrangler. miniflare options are merged over the Worker from cloudflare.config.ts, with miniflare values taking precedence. Config functions receive Vitest's mode as ctx.mode, which defaults to test and can be changed with --mode.

    If you're moving from experimental.newConfig, secrets are now read from Vite's envDir instead of the directory containing cloudflare.config.ts, and remote bindings authenticate with cf instead of Wrangler.

Patch Changes
  • #​16642 d38cb02 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-02

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

  • #​16623 51bbf8b Thanks @​petebacondarwin! - Deprecate shared tooling helper exports from Miniflare

    Miniflare continues to export getNodeCompat, NodeJSCompatMode, and getFreshSourceMapSupport for 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:

    import {
      getNodeCompat,
      type NodeJSCompatMode,
    } from "@cloudflare/workers-utils/node-compat";
    import { getFreshSourceMapSupport } from "@cloudflare/workers-utils/sourcemap";

    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.12

Compare Source

Patch Changes

v1.4.11

Compare Source

Patch Changes
  • #​15565 142230d Thanks @​luccamordente! - Flush console.log() calls made from another I/O context without waiting for the runner's next message

    Vitest 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 through SELF, a queue consumer, a waitUntil() 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 Thanks @​swalker326! - Fix Durable Object self-references in tests and container validation

    Durable Object bindings that explicitly name the Worker itself now resolve to the test runner in @cloudflare/vitest-plugin, for both cloudflare.config.ts and 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 --name or a CI name override preserves the intended Durable Object target.

  • Updated dependencies [ec0bea4, b4653b4, 25802bc, 25802bc, 15fbaed, d8899ac, 8b64bec]:

v1.4.10

Compare Source

Patch Changes

v1.4.9

Compare Source

Patch Changes
microsoft/playwright (@​playwright/test)

v1.65.0

Compare 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 --bun flag, because without it bunx playwright test runs on Node.js:

bunx --bun playwright test

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:

  • There is no watch mode. UI mode does not run tests again when files change, and --only-changed does not follow imports.
  • Bun loads modules itself, so --tsconfig and the JSX options in tsconfig.json have no effect, and custom ESM loaders are not supported.
  • Stack traces do not include async frames, and API names do not include the class name: click instead of locator.click. This changes some step locations, step titles and error messages.
  • Console output of a test does not get into the trace and UI mode.

🚨 Reports with only failures

New failures reporter prints failures and successful retries as they occur, followed by a summary, without progress output.

New onlyFailures option of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:

// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['failures'],
    ['html', { onlyFailures: true }],
  ],
});

🎯 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('restart the server', { lock: '-exclusive-' }, async () => {
      // No other test runs while this one is running.
    });
  • test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:

    test('upload a file', async ({ page }) => {
      test.skip('Not implemented yet');
    });
  • New PLAYWRIGHT_TRANSFORM_CACHE_DIR environment variable sets the directory for transpiled test files, for example on a Linux machine shared with other users.

New APIs

Notable Changes ⚠️

  • TypeScript class fields now follow useDefineForClassFields from your tsconfig.json, the same as tsc. It is enabled for ES2022 and later targets, and when target is not specified. A field initializer that reads a constructor parameter property now fails, because the initializer runs first:

    class LoginPage {
      // TypeError: Cannot read properties of undefined (reading 'getByRole')
      readonly submit = this.page.getByRole('button', { name: 'Submit' });
    
      constructor(private readonly page: Page) {}
    }

    Move the initialization to the constructor, or set "useDefineForClassFields": false in your tsconfig.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 inert attribute, 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-tests to 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=/api cookies for /apiv2, and a Path=/foo/ cookie does not match /foo. APIRequestContext sends a cookie without a name as Cookie: x instead of Cookie: =x, and stores Set-Cookie: token as a cookie without a name.

  • Proxy credentials are no longer sent to websites. The credentials in the proxy option now answer only proxy challenges. To authenticate on a website, use httpCredentials.

  • 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 URLSearchParams values of the params option in APIRequestContext requests are now appended to the query that the URL already has, instead of replacing it.

  • .css, .less and .scss imports 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 example a.spec.ts:3:7 instead of a.spec.ts:3:11. This is the same as in ESM.

Announcements

  • ⚠️ Playwright no longer tests on Node.js 20. Use Node.js 22, 24 or 26, as listed in the system requirements.
  • 🐳 Docker images now include Node.js 26 instead of Node.js 24, and the latest patch of Chromium on the same branch.

Browser Versions

  • Chromium 158.0.8127.18
  • Mozilla Firefox 159.0
  • WebKit 27.2

This version was also tested against the following stable channels:

  • Google Chrome 157
  • Microsoft Edge 156
getsentry/sentry-javascript (@​sentry/cloudflare)

v11.11.0

Compare Source

Important Changes
  • ref(cloudflare): Use the shared request handler wrapper (#​25588)

    Cloudflare Workers now use the same request handler wrapper as Deno.serve and Bun.serve. Changes for Cloudflare users:

    • Request spans now set client.address from the CF-Connecting-IP header (or another forwarding header), as on the other runtimes. This follows dataCollection.userInfo, which is true by default. To leave it out, set dataCollection: { userInfo: false }.
    • Request spans now have the response header attributes, and events have the response context with the status code.
    • When the source of a streamed response fails, the SDK now captures the error and marks the span as failed. With captureErrors: false, it does not capture it.
    • Request spans now list every Set-Cookie header of a response, as on Deno and Bun.
    • Without 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: true on nestIntegration() to send check-ins for every @Cron() method, without adding @SentryCron to each one. It's off by default. Each monitored job creates a monitor in Sentry, and monitors are billed. Use excludeCronJobs to skip jobs by slug. Methods that also have @SentryCron check in once, with the slug and options passed to @SentryCron.

  • feat(node): Add cronJobIntegration to monitor cron jobs (#​25477)

    Add Sentry.cronJobIntegration() to integrations to send check-ins for every named CronJob of the cron package (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. Use excludeJobs to skip jobs by name. Sentry.cron.instrumentCron is deprecated; use cronJobIntegration instead.

  • fix(server-utils): Instrument @​anthropic-ai/sdk 1.x and turn off its own OTel spans (#​25750)

    The Anthropic integration now instruments @anthropic-ai/sdk 1.x. Since 0.134 the SDK also records its own OpenTelemetry spans, such as anthropic.messages.create, which duplicated Sentry's gen_ai spans. Once Sentry instruments the SDK, it sets ANTHROPIC_OPEN_TELEMETRY=false to turn those spans off. To keep them, set ANTHROPIC_OPEN_TELEMETRY=true or pass the openTelemetry option 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 cacheComponents shell, the pageload now has the page.server_rendering.type attribute. It is static if the whole page came from the cache, and partially_static if 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
  • feat(astro): Add @sentry/astro/integration entry for the Astro integration (#​25726)
  • feat(bundler-plugins): Add sourcemaps.deleteSourcemapsAfterUpload and staged uploads (#​25637)
  • feat(nestjs): Derive SentryCron monitor config from @​Cron (#​25013)
  • feat(nextjs): Add applicationKeyExcludeDependencies option (#​25818)
  • feat(node): Add awsLambdaWebIntegration for Lambda Web Functions (#​25355)
  • feat(node): Add BullMQ integration (#​21777)
  • feat(node): Add nodeCronIntegration to monitor node-cron tasks (#​25473)
  • feat(node): Add nodeScheduleIntegration to monitor node-schedule jobs (#​25474)
  • feat(node): Support postgres v4 through its native tracing channels (#​26076)
  • feat(server-utils): Extract getSqlSpanName for SQL span names (#​25929)
  • feat(server-utils): Move to new getSqlQueryAttributes helper for consistency (#​25927)
  • feat(server-utils): Record AI SDK v7 runtime and tool context on Vercel AI spans (#​25774)
  • feat(server-utils): Set db.operation.name on SQL spans (#​25850)
  • feat(server-utils): Support @​mistralai/mistralai v3 (#​25827)
  • feat(solidstart): Export withSentry from @sentry/solidstart/vite (#​25725)
  • fix(astro): Initialize the server SDK on the first endpoint request (#​25731)
  • fix(browser): Attribute long animation frame spans to the longest script (#​25990)
  • fix(bundler-plugins): Inject debug IDs into every esbuild rebuild (#​26099)
  • fix(bundler-plugins): upload literal artifact paths (#​25356)
  • fix(cloudflare): Run build-time instrumentation in vite dev (#​25777)
  • fix(core): Call native toString without page-replaceable lookups in FunctionToString (#​25921)
  • fix(core): Enforce linked error limits for aggregate and suppressed errors (#​25873)
  • fix(core): Only create Supabase db spans when there is a parent span (#​25807)
  • fix(core): preserve span links through beforeSendSpan (#​25566)
  • fix(core): Respect header collection for session user agents (#​25871)
  • fix(deps): Bump glob to 14 and drop the direct dependency from react-router (#​26014)
  • fix(nextjs): Don't abort Cache Components renders on Cloudflare Workers when requests overlap (#​25315)
  • fix(nextjs): Drop tunnel requests under the Next.request proxy root span (#​26096)
  • fix(nextjs): Fork isolation scope for Next.request proxy root spans (#​26084)
  • fix(nextjs): Strip source map comments before trailing debug IDs (#​25881)
  • fix(nitro): Capture errors thrown in tasks (#​26089)
  • fix(nuxt): Keep storage instrumentation plugin synchronous (#​25949)
  • fix(replay): Skip buffered replays for captureMessage stacks from the attachStacktrace default (#​25846)
  • fix(server-utils): Fix orchestrion source maps of instrumented modules (#​25772)
  • fix(server-utils): Read the pi-durable session id in every phase outside a run (#​25838)
  • fix(server-utils): Require a parent span for Firestore operations (#​25855)
  • fix(server-utils): Require a parent span for Tedious queries (#​25822)
  • fix(server-utils): Use onlyIfParent for Firestore spans (#​25877)
  • fix(server-utils): Use onlyIfParent for Tedious spans (#​25876)
  • fix(solidstart): Serve the managed tunnel under Vite's base on SolidStart 2 (#​25848)
  • fix(sveltekit): Resolve Handle and ResolveOptions types on SvelteKit 3 (#​26085)
  • fix(wasm): Skip length prefix in 16-byte build IDs (#​24857)
  • ref(core): Deprecate the released handleTunnelRequest form and reword the serveTunnelIntegration docs (#​25844)
Internal Changes

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • Between 12:00 AM and 08:59 AM, only on Monday (* 0-8 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@khepri-bot
khepri-bot Bot requested a review from a team November 16, 2026 06:43
@khepri-bot khepri-bot Bot added the renovate label Nov 16, 2026
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch 8 times, most recently from f8bb047 to 6c837f2 Compare November 19, 2026 20:46
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch from 6c837f2 to c10a02c Compare November 20, 2026 20:31

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants