[khepri-bot]

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.62.5 → 1.64.0			devDependencies	minor	1.66.0 (+1)
@cloudflare/vitest-plugin (source)	1.4.0 → 1.4.4			devDependencies	patch	1.4.11 (+6)
@modelcontextprotocol/sdk (source)	1.32.0 → 1.32.1			dependencies	patch	1.32.2
@playwright/test (source)	1.63.0 → 1.64.1			devDependencies	minor
@sentry/cloudflare (source)	11.4.0 → 11.8.0			dependencies	minor	11.10.0 (+1)
@sentry/solid (source)	11.4.0 → 11.8.0			dependencies	minor	11.10.0 (+1)
@testing-library/user-event	14.6.7 → 14.6.8			devDependencies	patch
@types/node (source)	26.6.4 → 26.6.5			devDependencies	patch	26.6.6
actions/setup-node	v7.0.0 → v7.1.0			action	minor
daisyui (source)	5.7.47 → 5.7.50			devDependencies	patch
fake-indexeddb	6.2.5 → 6.2.6			devDependencies	patch	6.2.7
idb	8.0.3 → 8.0.4			dependencies	patch
pnpm (source)	12.9.1 → 12.14.0			packageManager	minor	12.16.1 (+2)
solid-js (source)	1.9.15 → 1.9.17			dependencies	patch	1.9.18
vite (source)	8.3.3 → 8.3.4			devDependencies	patch	8.3.5
vitest (source)	5.0.3 → 5.0.5			devDependencies	patch
wrangler (source)	4.147.0 → 4.151.1			devDependencies	minor	4.156.0 (+6)
zod (source)	4.6.6 → 4.6.7			dependencies	patch

---

Release Notes

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

v1.64.0

Compare Source

Minor Changes

• #​16245 d6b1c82 Thanks @​WalshyDev! - Generate source maps for Worker environments by default

  Worker builds now emit source maps unless Vite's build.sourcemap or the Worker's upload_source_maps is set, so deployed Workers get stack traces that point at the original source. The source maps are written next to the Worker bundle and included in Build Output; the client environment is unchanged, so no source maps are added to public assets. Set build.sourcemap: false for the Worker environment, or upload_source_maps: false in the Worker config, to opt out.

Patch Changes

• Updated dependencies [f360829, d6b1c82, 97b2fb1, 97b2fb1, acd2822]:
  • miniflare@5.20261012.0-beta
  • wrangler@​4.151.0

v1.63.2

Compare Source

Patch Changes

• #​16025 61e07fd Thanks @​kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds

  cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.

• #​16038 dc3e4df Thanks @​dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages

  Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.

• Updated dependencies [fcf625d, 091e5ec, 5152bf8, 9f87de8, daae435, 18f061c, 9be5ec7, 61e07fd, cafd3f9, ea64ec4, d232454]:

  • wrangler@​4.150.0
  • miniflare@5.20261006.2-beta

v1.63.1

Compare Source

Patch Changes

• #​15617 93c1069 Thanks @​jpatel3! - Stop the update check from recommending deprecated versions

  Previously, the "update available" notice shown by wrangler and @cloudflare/vite-plugin always pointed at whichever version was tagged latest on npm, even after that version had been deprecated for shipping a bug. Deprecated versions are now never recommended: if the latest release has been deprecated, the newest non-deprecated stable release below it is suggested instead, or nothing at all if you are already on it.

  The check now reads the npm registry directly instead of going through the update-check package, which discarded the deprecation information. The on-disk cache location and one-hour refresh interval are unchanged.

• #​16003 6947df3 Thanks @​oddharsh! - Ship using and await using declarations to the runtime as written

  Worker builds no longer lower explicit resource management into helper code, so Workers that use it ship about 1.7 KB less. workerd supports the syntax natively. On Vite 8 the plugin builds Workers at an es2026 target, so Oxc leaves the syntax alone. On Vite 6 and 7, where esbuild has no es2026 target, the Worker environments tell esbuild that using is supported instead. Client builds keep their own targets: the plugin changes only the Worker environments.

• #​16145 e820406 Thanks @​cpojer! - Honor the source-map setting in release builds

  Omit the plugin's JavaScript and declaration source maps when building with SOURCEMAPS=false, reducing the installed package size. Normal development builds keep source maps, and application source-map settings are unchanged.

• Updated dependencies [2d1d563, 85b14e7, e6f7663, fe607f9, ad7ff45, 8de6b3c, ae29445, 757faa6, cc8e969, 417b186, 93c1069, 6947df3, 82acf3c, 9a58244]:

  • miniflare@5.20261006.1-alpha
  • wrangler@​4.149.0

v1.63.0

Compare Source

Minor Changes

• #​16030 aa2f9b7 Thanks @​edmundhung! - Add email-protected Quick Tunnels to the Cloudflare Vite plugin

  Set tunnel.allowedMail to a list of email addresses or domain patterns to require email authentication when exposing a Vite development or preview server through a Quick Tunnel.

Patch Changes

• Updated dependencies [b4e1299, b75421f, 0ec13b7, 2b1a0ca, c492d63, ba52118, 946aaa7, 48f3c04, 14f0339, 5606a74, 4d308f6, f8cdcb9, e44cf6b, aa2f9b7, 42c7219, 2dde890, 26e03e2, 2dde890, 0b51fec]:
  • wrangler@​4.148.0
  • miniflare@5.20261006.0-alpha

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

v1.4.4

Compare Source

Patch Changes

• Updated dependencies [e1d1b77, e13d5cc, 42c6912, 4a5377f]:
  • miniflare@5.20261012.1-beta
  • wrangler@​4.151.1

v1.4.3

Compare Source

Patch Changes

• #​16248 ad01099 Thanks @​mattjohnsonpint! - Fix V8 coverage failing with Vitest 5.0.4

  Tests using V8 coverage with Vitest 5.0.4 no longer fail with an assertion error during teardown.

• #​16163 5f12934 Thanks @​edmundhung! - Fix Workers tests failing with Vitest's filesystem module cache

  This supports Vitest 4.1's test.experimental.fsModuleCache and Vitest 5's test.fsModuleCache.

v1.4.2

Compare Source

Patch Changes

• Updated dependencies [f360829, d6b1c82, 97b2fb1, 97b2fb1, acd2822]:
  • miniflare@5.20261012.0-beta
  • wrangler@​4.151.0

v1.4.1

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]:

  • wrangler@​4.156.0
  • miniflare@5.20261023.3-beta

modelcontextprotocol/typescript-sdk (@​modelcontextprotocol/sdk)

v1.32.1

Compare Source

What's Changed

• [v1.x] docs: state the principles in CLAUDE.md by @​claude[bot] in #​2939
• [v1.x] docs: point the README at v2 and say what v1.x supports by @​claude[bot] in #​2942
• chore: bump version to 1.32.1 by @​claude[bot] in #​2954

Full Changelog: modelcontextprotocol/typescript-sdk@1.32.0...1.32.1

microsoft/playwright (@​playwright/test)

v1.64.1

Compare Source

Bug Fixes

• #​43247 [Bug]: _electron.launch intermittently loses a packaged app's first window since 1.64.0
• #​43242 [Regression]: Chromium 155+ aborts a preflighted cross-origin redirect whenever any route is registered (net::ERR_ABORTED)

v1.64.0

Compare Source

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');

for (const tool of await page.webmcp.tools())
  console.log(tool.name, tool.description);

const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

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

export default defineConfig({
  use: {
    video: {
      mode: 'on',
      size: { width: 1920, height: 1080 },
      fps: 60,
      show: {
        actions: {
          style: {
            point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
            highlight: 'outline: 2px solid #​333; background: rgba(0, 128, 255, .15)',
            title: 'font-size: 16px',
          },
        },
      },
    },
  },
});

• New fps option in testOptions.video, recordVideo and
  screencast.start(). Firefox and WebKit currently capture up to 25 frames per second.
• New style option takes CSS declarations for the point marker, the target
  highlight and the action title. It replaces the fontSize option, which is now deprecated.
• The cursor stays visible at the last action point, survives navigations and travels along a natural, eased path.
• Videos are encoded with VP9 instead of VP8, which takes less CPU and produces smaller files of the same or better
  quality.
• All video options are also available in Playwright MCP and playwright-cli.

🎯 Test runner

• New testProject.default option keeps a project in the config without running it by default. You can configure every browser you care about, and let a plain npx playwright test run just your favourite one:

  // playwright.config.ts
  import { defineConfig, devices } from '@playwright/test';
  
  export default defineConfig({
    projects: [
      { name: 'chromium', use: devices['Desktop Chrome'] },
      { name: 'firefox', use: devices['Desktop Firefox'], default: false },
      { name: 'webkit', use: devices['Desktop Safari'], default: false },
    ],
  });

  npx playwright test                     # runs chromium only
  npx playwright test --project=firefox   # runs firefox
  npx playwright test --project="*"       # runs all three, for example on CI

• New --shuffle command line option schedules tests in a random order, which helps to find tests that accidentally depend on each other.

  npx playwright test --shuffle
  # Running 42 tests using 4 workers, shuffle seed 271828182
  # ...
  
  # Pass the seed to reproduce the same order.
  npx playwright test --shuffle 271828182

• New lock option in test.describe.configure() adds test locks to all tests in a file or a group:

  test.describe.configure({ lock: 'user-settings' });

• New type option of toHaveScreenshot in testConfig.expect stores all unnamed screenshots as WebP:

  // playwright.config.ts
  export default defineConfig({
    expect: {
      toHaveScreenshot: { type: 'webp' },
    },
  });

🪆 Locator.within()

New locator.within() combines two locators that you already have, reading in the natural order —
"this button, within that dialog":

const saveButton = page.getByRole('button', { name: 'Save' });
const dialog = page.getByTestId('settings-dialog');

await saveButton.within(dialog).click();

Relative locators such as locator.nth() or locator.first() are resolved inside each parent
separately, which makes column-like queries straightforward:

// The third cell of every row, not the third cell in the table.
const thirdColumn = page.getByRole('cell').nth(2).within(page.getByRole('row'));
await expect(thirdColumn).toHaveText(['Apple', 'Banana', 'Cherry']);

New APIs

• New page.getByRef() locates an element by its aria ref, such as e2, reported by page.ariaSnapshot() in the 'ai' mode.

• New option includeShadow in page.content() and frame.content() serializes open shadow roots as declarative shadow DOM.

• New option signCount sets the initial signature counter of a virtual credential. credentials.create() and credentials.get() return the current signCount, and it is saved and restored together with the credentials in the storage state.

• New fullConfig.filteredProjects lists the projects that were selected to run after applying the --project filter. It is available in global setup and reporters.

• New apiRequestContext.addCookies(), apiRequestContext.cookies() and apiRequestContext.clearCookies() manage cookies of a request context, mirroring the BrowserContext methods:

  await request.addCookies([{ name: 'session-id', value: '42', url: 'https://example.com' }]);
  console.log(await request.cookies('https://example.com'));
  await request.clearCookies({ name: 'session-id' });

Breaking changes ⚠️

• screen property is now forwarded from the device descriptors. If you use ...devices['Desktop Chrome'] and alike, window.screen and media queries now see the emulated screen size. You can opt-out by explicitly setting screen to undefined:

  // playwright.config.ts
  export default defineConfig({
    use: {
      ...devices['Desktop Chrome'],
      screen: undefined,
    },
  });

• JSX in your test files now follows your tsconfig.json. Playwright compiles JSX in test files according to the jsx, jsxFactory, jsxFragmentFactory and jsxImportSource tsconfig options, and defaults to the automatic runtime from react/jsx-runtime.

• --update-snapshots=missing now passes the test run. Tests that only create missing snapshots now pass in the 'missing' mode of testConfig.updateSnapshots, so that CI can generate new snapshots and verify the existing ones in a single run. The mode used when the option is not specified is now called 'default' and behaves as before: missing snapshots are written and the test fails.

• Elements inside hidden iframes are considered hidden. Elements inside an iframe that is not visible, for example with visibility: hidden, are now considered hidden by actions, locator.isVisible() and expect(locator).toBeVisible().

Browser Versions

• Chromium 156.0.8078.4
• Mozilla Firefox 157.0
• WebKit 27.2

This version was also tested against the following stable channels:

• Google Chrome 155
• Microsoft Edge 155

getsentry/sentry-javascript (@​sentry/cloudflare)

v11.8.0

Compare Source

Important Changes

• feat(bundler-plugins): Release @sentry/webpack-plugin, @sentry/vite-plugin, @sentry/rollup-plugin and @sentry/esbuild-plugin from the SDK repository (#​25095)

  The four standalone bundler plugins now release together with the SDK, so their version jumps from 5.4.1 to the SDK version. Each package re-exports the matching @sentry/bundler-plugins entry point, which we recommend for new projects. The plugin options do not change, but the update brings these breaking changes:

  • Node.js 20.19.0 or higher is required.
  • @sentry/webpack-plugin requires webpack 5.1 or higher. The @sentry/webpack-plugin/webpack5 entry point still works and exports the same plugin as @sentry/webpack-plugin.
  • The plugins use the sentry CLI SDK instead of @sentry/cli. Sentry self-hosted 26.4.2 or higher is supported. Lower versions may continue to work.
  • Deploys that the plugins create on Vercel use the value of VERCEL_TARGET_ENV (production, preview or a custom name) as their environment, instead of vercel-production or vercel-preview. To keep the old value, set release.deploy.env.

• feat(server-utils): Instrument the OpenAI decisions API as gen_ai.decide spans (#​25285)

  OpenAI decisions.create calls now create gen_ai.decide spans.

Other Changes

• feat(core): Support SuppressedError in LinkedErrors integration (#​25246)
• fix(astro): Delete generated source maps for static output (#​25310)
• fix(astro): Upload source maps of Astro 7's prerender build (#​25309)
• fix(browser): Apply urlQueryParams to the Referer header (#​25324)
• fix(cloudflare): auto-instrument when wrangler main is a package (#​25343)
• fix(hono): Expose runtime-specific SDK options (#​25290)
• fix(node): Instrument Prisma 8 CollectionBase from rc.15 (#​25301)
• fix(nuxt): Skip 3xx/4xx Nuxt errors in the vue:error hook (#​25341)
• fix(server-utils): Read pi-durable 1.2.0 tool results from output (#​25312)
• fix(server-utils): Transform modules once when two Sentry Vite plugins add orchestrion (#​25043)
• fix(sveltekit): add op and origin to Kit's sveltekit.endpoint span (#​25376)
• fix(tanstackstart-react): Keep parametrized route names in Nitro 3 builds (#​25307)
• fix(tanstackstart-react): Rewrite source paths of split route modules (#​25361)

Internal Changes

• chore: Add external contributor to CHANGELOG.md (#​25375)
• ci: Install the pnpm version that Volta pins (#​25287)
• license: Add cli FSL notice to package licenses (#​25314)
• ref(core): use shared MCP attribute conventions (#​25059)
• ref(tanstackstart-react): Reuse shared component annotation options (#​25313)
• test(browser): Keep whitespace text out of the handlers-lcp page (#​25280)
• test(bun): Restore @​sentry/core spies after the Bun.serve tests (#​25276)
• test(bundler-plugins): Disable CLI telemetry in the CLI contract tests (#​25308)
• test(e2e): Add node-openai-decisions-send-to-sentry test app (#​25331)
• test(e2e): Add node-openai-send-to-sentry test app (#​24824)
• test(e2e): Add nuxt-5-sourcemaps test (#​25268)
• test(e2e): Inherit root Volta config in all e2e test apps (#​25369)
• test(e2e): Use an external host address for the Lambda DSN on loopback hostnames (#​25282)
• test(nextjs): Run nextjs-16-tunnel on Cloudflare (#​25161)
• test(nextjs): Switch DEBUG_BUILD with a getter instead of re-importing the SDK (#​25279)
• test(node): Await the child exit in the "should exit" integration tests (#​25277)
• test(node): Cover ioredis v6 in the diagnostics_channel suite (#​25300)
• test(node): Cover LangChain model calls made from a tool without config (#​25326)
• test(node): Log slow and failed Docker Compose starts in integration tests (#​25278)
• test(node): Unflake captureMessage with_level test (#​25358)
• test(sveltekit): Pin rollup to 4.64.5 (#​25328)

Work in this release was contributed by @​kunal649 and @​mketiku. Thank you for your contributions!

v11.7.0

Compare Source

Important Changes

• feat(cloudflare): Add opt-in cron monitoring for Cron Triggers (#​25014)

  The new cronTriggersIntegration sends check-ins for Cron Triggers. Each check-in includes the schedule from controller.cron, so Sentry creates the monitor on the first run. The integration is opt-in, because monitors are billed.

  Cron Triggers have no names, so map each cron expression of your wrangler config to a monitor slug. With the Sentry Cloudflare Vite plugin, add the integration to src/instrument.server.ts:

  // src/monitorSlugs.ts
  export const monitorSlugs: Record<string, string> = {
    '30 9 * * MON-FRI': 'daily-report',
  };
  
  // src/instrument.server.ts
  import * as Sentry from '@sentry/cloudflare';
  import { monitorSlugs } from './monitorSlugs';
  
  export default Sentry.defineCloudflareOptions(env => ({
    dsn: env.SENTRY_DSN,
    integrations: [Sentry.cronTriggersIntegration({ monitorSlug: cron => monitorSlugs[cron] })],
  }));
  
  // src/index.ts
  import { monitorSlugs } from './monitorSlugs';
  
  export default {
    async scheduled(controller, env) {
      switch (monitorSlugs[controller.cron]) {
        case 'daily-report':
          // Your daily report job
          break;
      }
    },
  };

  The monitorSlug function can also return monitor settings, for example { monitorSlug: 'daily-report', maxRuntime: 30 }, or undefined to send no check-ins for a trigger. Without monitorSlug, the SDK derives the slug from the cron expression. If you deploy with wrangler directly, pass the same integration to Sentry.withSentry.

• feat(node): Add neonIntegration for @​neondatabase/serverless (#​25164, #​25176)

  The new neonIntegration creates db spans for queries of the @neondatabase/serverless driver: for the WebSocket Client and Pool, and for the HTTP neon() function. This includes the neon-http and neon-serverless adapters of Drizzle. The integration is on by default when tracing is enabled.

• feat(node): Stop sending the process session once request sessions are tracked (#​24915)

  Node servers sent release health data two times: as request session aggregates, and as the process session of processSessionIntegration. An error in a request also marked the process session as errored, so the SDK counted the error two times. Now the SDK drops the process session when it tracks the first request session. Scripts, CLIs and workers that do not serve requests keep the process session, and so do servers with httpServerIntegration({ sessions: false }). This changes the release health numbers of Node servers, because they no longer send the errored or crashed update of the process session.

• feat(server-utils): Record decide calls as gen_ai.decide spans (#​25270, #​25272, #​25274, #​25281)

  Vercel AI experimental_decide calls, Mastra classifier evaluations, TypeSafe and LangChain Jev calls, and Workers AI calls to TypeSafe Jev and Cloudflare Clef models now create decide <model> spans with the op gen_ai.decide. Before, these spans had the op gen_ai.evaluate, which is now deprecated in the Sentry conventions. If you use gen_ai.evaluate in queries, alerts or dashboards, change it to gen_ai.decide.

• fix(browser): Apply urlQueryParams to more URLs (#​25262, #​25289)

  The dataCollection.urlQueryParams option now also filters the query parameters of these URLs:

  • the page URL in event.request.url
  • the browser.* and resource.* span names with traceLifecycle: 'static'
  • the LCP URL attributes lcp.url and browser.web_vital.lcp.url
  • the URLs in fetch, XHR and navigation breadcrumbs
  • the ui.element.url attribute of elementTimingIntegration

  Before this fix, these URLs could send sensitive query values, for example ?jwt=..., to Sentry.

• fix(nextjs): Apply top-level bundleSizeOptimizations to webpack and Turbopack builds (#​24818)

  The top-level bundleSizeOptimizations option now removes unused SDK code in webpack and in Turbopack builds. Before, the tree-shaking options had no effect on Turbopack. The webpack.treeshake option is deprecated. It still works, but when you set both options, bundleSizeOptimizations takes precedence.

Other Changes

• feat(nuxt): Detect the server API with @nuxt/kit 4.6 (#​25138)
• fix(bundler-plugins): Escape JSON in generated injection code (#​25265)
• fix(core): Don't mark http client spans as errors when the caller aborts (#​25260)
• fix(core): Record span client report outcomes when discarding transactions (#​25006)
• fix(core): Record client outcomes when beforeSend callbacks return invalid values (#​25049)
• fix(core): Record span outcomes for spans dropped when building a transaction (#​25048)
• fix(core): Report actual item count in client reports of envelope send failures (#​25185)
• fix(core): Strip internal custom span name from streamed spans (#​25212)
• fix(nextjs): Filter query parameters in request error context (#​25233)
• fix(node): Don't mark fetch spans as errors when the caller aborts (#​25129)
• fix(nuxt): Delete public source maps before Nitro lists its public assets (#​25267)
• fix(nuxt): Keep @sentry/server-runtime-injection external on Nitro v3 (#​24901)
• fix(nuxt): Remove @​opentelemetry/resources dev alias (#​25216)
• fix(profiling-node): Stop the trace lifecycle profiler when spans are unsampled (#​25210)
• fix(react-router): Respect custom default integrations (#​25259)
• fix(remix): Respect custom default integrations (#​25258)
• fix(server-utils): avoid quadratic SQL summary regex backtracking (#​25255)
• fix(server-utils): End Express layer spans when the client aborts (#​25209)
• fix(server-utils): Record amqplib consumer info before the first delivery and instrument the callback API (#​25047)
• fix(server-utils): Stop treating previous_response_id as the OpenAI conversation id (#​25269)
• fix(sveltekit): Read load event pathname untracked (#​25235)
• fix(sveltekit): Stop adapter-node 6 output dir probe from deleting the build (#​25193)

Internal Changes

• chore: Add external contributor to CHANGELOG.md (#​25230)
• chore: Add external contributor to CHANGELOG.md (#​25271)
• chore(deps-dev): Bump oxlint-tsgolint from 7.0.2001 to 7.0.2003 (#​25237)
• chore(deps-dev): Bump rimraf from 5.0.10 to 6.1.3 (#​25241)
• chore(deps): Bump @sentry/conventions to 0.27.0 (#​25264)
• chore(deps): Bump next from 16.2.11 to 16.3.8 in /dev-packages/e2e-tests/test-applications/nextjs-16 (#​25179)
• chore(deps): Bump next from 16.2.11 to 16.3.8 in /dev-packages/e2e-tests/test-applications/nextjs-16-tunnel (#​25190)
• chore(size-limit): weekly auto-bump (#​25213)
• ci: Install Playwright in the background during E2E app builds (#​25207)
• ci: Run lint steps in parallel (#​25187)
• ci(bun): Test the oldest supported Bun version and the newest 1.4 (#​25203)
• docs: Scope pre-PR tests to affected suites (#​25198)
• feat(deps): Bump @​aws-sdk/client-kinesis from 3.1068.0 to 3.1146.0 (#​25240)
• feat(deps): Bump handlebars from 4.7.9 to 4.7.10 (#​25206)
• feat(deps): Bump pino from 9.10.0 to 10.4.0 (#​25238)
• feat(deps): Bump reflect-metadata from 0.2.1 to 0.2.2 (#​25239)
• ref(core): Simplify transport item loss recording (#​25224)
• ref(server-utils): Export the pg query span helpers ([#&feat(events): replaces notifications gate with Events API polling #82

[!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.