1) [chromium] › tests/orpc-error.test.ts:4:1 › should capture server-side orpc error ───────────── Error: page.waitForTimeout: Test timeout of 30000ms exceeded. 11 | 12 | await page.goto('/'); > 13 | await page.waitForTimeout(500); | ^ 14 | await page.getByRole('link', { name: 'Error' }).click(); 15 | 16 | const orpcError = await orpcErrorPromise; at /home/runner/work/_temp/test-application/tests/orpc-error.test.ts:13:14

[chromium] › tests/orpc-error.test.ts:4:1 › should capture server-side orpc error: ../../_temp/test-application/tests/orpc-error.test.ts#L0

1) [chromium] › tests/orpc-error.test.ts:4:1 › should capture server-side orpc error ───────────── Test timeout of 30000ms exceeded.

[chromium] › tests/trpc-mutation.test.ts:4:1 › should create transaction with trpc input for mutation: ../../_temp/test-application/tests/trpc-mutation.test.ts#L0

2) [chromium] › tests/trpc-mutation.test.ts:4:1 › should create transaction with trpc input for mutation Test timeout of 30000ms exceeded.

[chromium] › tests/trpc-error.test.ts:4:1 › should capture error with trpc context: ../../_temp/test-application/tests/trpc-error.test.ts#L0

1) [chromium] › tests/trpc-error.test.ts:4:1 › should capture error with trpc context ──────────── Test timeout of 30000ms exceeded.

Build

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dkhunt27/action-nx-affected-list@v6.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Size Check

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./dev-packages/size-limit-gh-action. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node (20) Unit Tests

❌ Project coverage check failed: 64.27% (-0.68%) relative to base

Node (20) Unit Tests

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: packages/browser/src/integrations/culturecontext.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js, /home/runner/work/sentry-javascript/sentry-javascript/packages/astro/scripts/syncIntegration.ts This usually indicates a path format mismatch between your coverage tool and the repository.

Node (24) Unit Tests

❌ Project coverage check failed: 64.27% (-0.64%) relative to base

Node (24) Unit Tests

Node (18) Unit Tests

❌ Project coverage check failed: 61.50% (-2.53%) relative to base

Node (18) Unit Tests

Node (22) Unit Tests

❌ Project coverage check failed: 64.27% (-0.64%) relative to base

Node (22) Unit Tests

Browser Unit Tests

❌ Patch coverage check failed: 33.33% < target 80%

ref(browser): Use safeSetSpanJSONAttributes in cultureContext integration #46306

Summary

build.yml

Annotations

ref(browser): Use `safeSetSpanJSONAttributes` in cultureContext integration #46306