You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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:
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:
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.
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)
Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) ([#20663](h
[!IMPORTANT]
✂ PR body was truncated to here.
Configuration
📅 Schedule: (in timezone Asia/Jakarta)
Branch creation
"before 7am on monday"
Automerge
At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
If you want to rebase/retry this PR, check this box
To trigger a single review, invoke the @coderabbitai review command.
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: 7e5a28d2-a1c8-4949-9198-7726d10070a4
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
Trigger review
Note
Reviews paused
It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.
aethera-deeptech/frontend#17: Configures Vitest for design tests; this PR updates Vitest and its coverage package.
Merge Risk: Minimal · previous review f884a
No merge-blocking issue is identified. Run the normal checks before merging.
Architecture risk: Low · up to f884a
The change affects 1 system.
Changed systems:package.json
Architecture concerns
No architecture-level concerns identified.
Review details
Systems and components
observed — package.json (service) was modified; 1 changed file maps to changed impact.
Before / after behavior
observed — Modified behavior in package.json: Updated @hookform/resolvers from 7.0.0 to 7.0.1 and @tanstack/react-query from 5.105.0 to 5.105.2; the other dependencies in this range are unchanged.
observed — Modified behavior in package.json: Updated @types/node from 26.6.5 to 26.6.6, @vitejs/plugin-react from 6.1.2 to 6.2.1, @vitest/coverage-v8 from 5.0.5 to 5.1.0, eslint-plugin-playwright from 2.12.1 to 2.12.2, and globals from 17.13.0 to 17.14.0. Other entries in this range are unchanged.
observed — Modified behavior in package.json: Updated vitest from 5.0.5 to 5.1.0.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title identifies the npm dependency updates, which are the main change in this pull request.
Description check
The description lists the dependency version updates and relevant release notes, so it relates directly to the changeset.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: d16a0756-ec9b-4dbd-8ddb-4eca546e98e9
Commits
Reviewing files that changed from the base of the PR and between 8345370 and f884a23.
Files ignored due to path filters: 1
package-lock.json is excluded by !**/package-lock.json
Files selected for processing: 1
package.json
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EALLOWREMOTE
npm error Fetching packages of type "remote" have been disabled
npm error Refusing to fetch "https://registry.npmjs.org/@tailwindcss/oxide-wasm32-wasi/-/oxide-wasm32-wasi-4.3.5.tgz"
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-16T01_34_45_347Z-debug-0.log
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
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:
7.0.0→7.0.51.64.1→1.65.011.10.0→11.11.010.6.5→10.6.610.6.5→10.6.64.3.3→4.3.55.105.0→5.107.126.6.5→26.6.66.1.2→6.2.15.0.5→5.1.02.12.1→2.12.210.6.5→10.6.614.0.3→14.0.417.13.0→17.14.010.6.5→10.6.64.3.3→4.3.58.3.5→8.3.65.0.5→5.1.0Release Notes
react-hook-form/resolvers (@hookform/resolvers)
v7.0.5Compare Source
Bug Fixes
v7.0.4Compare Source
Bug Fixes
v7.0.3Compare Source
Bug Fixes
v7.0.2Compare Source
Bug Fixes
v7.0.1Compare Source
Bug Fixes
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/react)
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
canaryVariants(#25866)36c7292to01bcb7f(#25954)requiresParentSpanin favor ofonlyIfParent(#25926)canaryVariants(#25865)nuxt-5 (tunnel-dev)e2e variant optional (#26004)Work in this release was contributed by @lazerg, @chiliec, @61465, @jpdefo, and @AyeshaWaseemAhmad. Thank you for your contributions!
storybookjs/storybook (@storybook/addon-a11y)
v10.6.6Compare Source
tailwindlabs/tailwindcss (@tailwindcss/vite)
v4.3.5Compare Source
Fixed
matchVariantplugin with thousands of values) ([#20663](hConfiguration
📅 Schedule: (in timezone Asia/Jakarta)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.