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

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

Process completed with exit code 1.

1) [chromium] › suites/integrations/supabase/db-operations/test.ts:31:11 › should capture Supabase database operation breadcrumbs Error: expect(received).toContainEqual(expected) // deep equality Expected value: {"category": "db.insert", "data": ObjectContaining {"query": ArrayContaining ["filter(columns, )"]}, "message": "insert(...) filter(columns, ) from(todos)", "timestamp": Any<Number>, "type": "supabase"} Received array: [{"category": "db.insert", "data": {"query": ["filter(columns, )"]}, "message": "insert filter(columns, ) from(todos)", "timestamp": 1777024082.907, "type": "supabase"}, {"category": "db.select", "data": {"query": ["select(*)"]}, "message": "select(*) from(todos)", "timestamp": 1777024082.918, "type": "supabase"}] 41 | 42 | expect(eventData.breadcrumbs).toBeDefined(); > 43 | expect(eventData.breadcrumbs).toContainEqual({ | ^ 44 | timestamp: expect.any(Number), 45 | type: 'supabase', 46 | category: 'db.insert', at /home/runner/work/sentry-javascript/sentry-javascript/dev-packages/browser-integration-tests/suites/integrations/supabase/db-operations/test.ts:43:33

Process completed with exit code 1.

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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: denoland/setup-deno@v2.0.3. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: denoland/setup-deno@v2.0.3. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: denoland/setup-deno@v2.0.3. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/setup-sam@v2. 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/

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: dev-packages/browser-integration-tests/suites/integrations/supabase/db-operations/init.js, dev-packages/e2e-tests/test-applications/supabase-nextjs/tests/performance.test.ts, packages/core/src/integrations/supabase.ts, packages/core/test/lib/integrations/supabase.test.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js, /home/runner/work/sentry-javascript/sentry-javascript/packages/browser/src/client.ts This usually indicates a path format mismatch between your coverage tool and the repository.

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/

3 passed (2.5s)

3 passed (2.5s)

2 passed (4.1s)

4 passed (4.5s)

4 passed (2.2s)

3 skipped 17 passed (2.7s)

3 passed (3.8s)

4 passed (7.3s)

5 passed (7.9s)

1 passed (4.4s)

22 passed (8.2s)

7 passed (6.2s)

4 passed (7.1s)

5 passed (8.3s)

3 passed (3.3s)

11 passed (2.9s)

3 passed (3.2s)

5 passed (8.3s)

3 passed (7.2s)

1 passed (1.9s)

1 passed (3.4s)

2 passed (4.4s)

12 passed (6.5s)

1 passed (6.1s)

4 passed (4.3s)

14 passed (4.8s)

3 passed (8.2s)

3 passed (14.7s)

7 passed (12.0s)

8 passed (2.5s)

3 passed (12.5s)

7 passed (9.4s)

2 passed (2.2s)

11 passed (5.3s)

11 passed (5.6s)

4 passed (2.2s)

3 passed (2.5s)

3 passed (3.5s)

4 passed (6.9s)

3 skipped 18 passed (3.6s)

7 passed (6.3s)

3 passed (18.6s)

10 passed (5.2s)

10 passed (5.6s)

8 passed (7.1s)

9 passed (10.0s)

12 passed (8.3s)

10 passed (10.4s)

11 passed (16.0s)

4 passed (2.8s)

15 passed (10.5s)

3 passed (6.2s)

3 passed (3.4s)

9 passed (9.1s)

10 passed (6.2s)

10 passed (6.2s)

12 passed (6.5s)

1 passed (5.0s)

1 skipped 20 passed (4.2s)

5 passed (9.2s)

4 passed (7.8s)

10 passed (26.6s)

5 passed (19.0s)

2 passed (2.1s)

13 passed (12.4s)

5 passed (9.2s)

1 passed (5.0s)

5 passed (7.4s)

13 passed (28.3s)

5 passed (8.0s)

1 skipped 20 passed (2.9s)

13 passed (25.9s)

1 skipped 14 passed (12.0s)

3 skipped 17 passed (1.6s)

5 passed (21.9s)

4 passed (8.0s)

9 passed (11.5s)

8 passed (3.2s)

8 passed (3.2s)

9 passed (11.2s)

3 skipped 21 passed (17.3s)

12 passed (6.8s)

1 passed (5.1s)

10 passed (27.6s)

12 skipped 1 passed (2.6s)

10 passed (36.7s)

3 passed (4.9s)

9 passed (11.6s)

40 passed (19.4s)

9 passed (12.5s)

2 passed (22.5s)

9 passed (12.2s)

2 skipped 19 passed (24.5s)

11 passed (15.9s)

23 passed (16.7s)

10 passed (26.5s)

16 passed (23.5s)

9 passed (10.8s)

1 skipped 12 passed (5.4s)

3 passed (17.3s)

3 passed (9.4s)

12 passed (28.4s)

13 passed (28.6s)

15 passed (21.8s)

16 passed (28.5s)

4 passed (10.8s)

29 passed (28.7s)

18 passed (19.3s)

12 passed (27.4s)

14 skipped 12 passed (21.4s)

12 passed (27.9s)

40 passed (18.7s)

5 passed (21.9s)

8 passed (9.8s)

4 passed (10.4s)

12 passed (29.0s)

4 passed (10.2s)

10 passed (37.6s)

11 passed (18.7s)

12 passed (27.3s)

3 passed (2.7s)

8 passed (6.8s)

14 passed (25.5s)

3 passed (17.4s)

3 passed (9.3s)

5 passed (19.9s)

11 passed (4.9s)

11 passed (5.2s)

12 skipped 1 passed (4.4s)

8 passed (28.8s)

12 passed (19.9s)

2 skipped 19 passed (25.3s)

7 passed (7.4s)

4 passed (19.1s)

4 passed (4.3s)

24 passed (16.0s)

12 passed (28.6s)

12 skipped 1 passed (6.3s)

18 passed (17.3s)

5 passed (10.8s)

8 passed (30.8s)

9 passed (9.2s)

14 skipped 12 passed (21.8s)

1 passed (3.1s)

1 passed (3.7s)

3 skipped 27 passed (37.5s)

30 passed (12.1s)

14 skipped 12 passed (21.5s)

4 passed (36.1s)

4 passed (7.4s)

3 passed (38.9s)

3 passed (6.7s)

4 skipped 10 passed (27.1s)

4 skipped 10 passed (7.4s)

13 passed (45.8s)

13 passed (9.5s)

2 flaky [chromium] › tests/trpc-error.test.ts:4:1 › should capture error with trpc context ───────────── [chromium] › tests/trpc-mutation.test.ts:4:1 › should create transaction with trpc input for mutation 1 passed (38.8s)

3 passed (4.0s)

3 skipped 27 passed (42.7s)

30 passed (12.3s)

17 passed (57.1s)

4 skipped 10 passed (29.1s)

2 skipped 12 passed (8.4s)

12 skipped 1 passed (4.4s)

13 passed (48.0s)

13 passed (8.7s)

13 passed (50.0s)

13 passed (8.5s)

3 passed (36.2s)

3 passed (10.3s)

4 skipped 10 passed (30.8s)

2 skipped 12 passed (7.5s)

5 passed (42.8s)

5 passed (11.7s)

4 passed (17.8s)

51 passed (1.0m)

4 passed (15.1s)

2 skipped 48 passed (59.6s)

2 skipped 29 passed (1.2m)

2 skipped 29 passed (37.3s)

7 skipped 23 passed (10.4s)

8 skipped 22 passed (10.1s)

5 skipped 25 passed (12.1s)

7 skipped 23 passed (10.3s)

4 passed (18.8s)

51 passed (1.0m)

4 skipped 26 passed (18.2s)

1 skipped 29 passed (19.8s)

5 skipped 25 passed (20.3s)

15 passed (26.3s)

479 skipped 190 passed (36.3s)

5 skipped 36 passed (1.7m)

2 skipped 39 passed (1.0m)

5 skipped 36 passed (1.7m)

2 skipped 39 passed (1.0m)

474 skipped 195 passed (37.9s)

43 passed (2.2m)

2 skipped 29 passed (2.0m)

2 skipped 29 passed (36.6s)

5 skipped 36 passed (1.9m)

2 skipped 39 passed (1.0m)

478 skipped 191 passed (40.4s)

2 skipped 29 passed (2.1m)

2 skipped 29 passed (38.0s)

342 skipped 327 passed (1.5m)

344 skipped 325 passed (1.5m)

5 skipped 29 passed (1.8m)

6 skipped 28 passed (1.1m)

4 passed (24.5s)

7 skipped 34 passed (3.0m)

2 skipped 39 passed (1.0m)

7 skipped 34 passed (2.9m)

2 skipped 39 passed (60.0s)

2 skipped 32 passed (2.6m)

2 skipped 32 passed (1.1m)

3 skipped 164 passed (2.5m)

7 skipped 34 passed (3.0m)

2 skipped 39 passed (1.0m)

2 skipped 32 passed (3.0m)

2 skipped 32 passed (1.1m)

1 failed [chromium] › suites/integrations/supabase/db-operations/test.ts:31:11 › should capture Supabase database operation breadcrumbs 1 skipped 166 passed (2.5m)

5 skipped 162 passed (3.6m)

3 skipped 164 passed (3.8m)

187 skipped 482 passed (3.9m)

192 skipped 477 passed (3.9m)

199 skipped 470 passed (3.7m)

56 skipped 613 passed (4.7m)

53 skipped 616 passed (4.7m)

56 skipped 613 passed (4.7m)

51 skipped 618 passed (4.8m)