Skip to content

feat(nextjs): Filter unwanted segments when span streaming is enabled #45915

feat(nextjs): Filter unwanted segments when span streaming is enabled

feat(nextjs): Filter unwanted segments when span streaming is enabled #45915

Triggered via pull request April 17, 2026 11:04
Status Failure
Total duration 18m 10s
Artifacts 11

build.yml

on: pull_request
job_get_metadata  /  Get Metadata
9s
job_get_metadata / Get Metadata
Check lockfile
2m 54s
Check lockfile
Check file formatting
43s
Check file formatting
Check PR branches
4s
Check PR branches
Prepare E2E tests
2m 51s
Prepare E2E tests
Matrix: job_browser_loader_tests
Matrix: job_browser_playwright_tests
Matrix: job_node_core_integration_tests
Matrix: job_node_integration_tests
Matrix: job_node_unit_tests
Matrix: job_remix_integration_tests
Size Check
1m 55s
Size Check
Lint
1m 1s
Lint
Circular Dependency Check
1m 30s
Circular Dependency Check
Upload Artifacts
0s
Upload Artifacts
Browser Unit Tests
1m 46s
Browser Unit Tests
Bun Unit Tests
0s
Bun Unit Tests
Deno Unit Tests
0s
Deno Unit Tests
Cloudflare Integration Tests
1m 52s
Cloudflare Integration Tests
Bun Integration Tests
0s
Bun Integration Tests
Check for faulty .d.ts files
45s
Check for faulty .d.ts files
Matrix: job_e2e_tests
Matrix: job_optional_e2e_tests
All required jobs passed or were skipped
5s
All required jobs passed or were skipped
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 54 warnings, and 64 notices
Node (22) Unit Tests
Process completed with exit code 1.
Node (20) Unit Tests
Process completed with exit code 1.
Node (18) Unit Tests
Process completed with exit code 1.
Node (24) Unit Tests
Process completed with exit code 1.
E2E nextjs-16 (canary, turbopack) Test (optional)
Process completed with exit code 1.
[chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL: ../../_temp/test-application/tests/server-components.test.ts#L0
1) [chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL Retry #3 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.
[chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL: ../../_temp/test-application/tests/server-components.test.ts#L0
1) [chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.
[chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL: ../../_temp/test-application/tests/server-components.test.ts#L0
1) [chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.
[chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL: ../../_temp/test-application/tests/server-components.test.ts#L0
1) [chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL Test timeout of 30000ms exceeded.
All required jobs passed or were skipped
Process completed with exit code 1.
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/
eslint(no-unused-vars): packages/core/test/lib/utils/weakRef.test.ts#L1
Identifier 'beforeEach' is imported but never used.
eslint(no-unused-vars): packages/core/test/lib/utils/weakRef.test.ts#L1
Identifier 'afterEach' is imported but never used.
eslint(no-unused-vars): packages/opentelemetry/test/utils/contextData.test.ts#L3
Identifier 'vi' is imported but never used.
eslint(no-unused-vars): packages/opentelemetry/test/utils/contextData.test.ts#L3
Identifier 'beforeEach' is imported but never used.
eslint(no-unused-vars): packages/opentelemetry/test/utils/contextData.test.ts#L3
Identifier 'afterEach' is imported but never used.
eslint(no-unused-vars): packages/core/src/integrations/requestdata.ts#L2
Identifier 'hasSpanStreamingEnabled' is imported but never used.
Node (22) Unit Tests
Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: packages/nextjs/src/client/index.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js This usually indicates a path format mismatch between your coverage tool and the repository.
Browser Unit Tests
Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: packages/nextjs/src/client/index.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js This usually indicates a path format mismatch between your coverage tool and the repository.
Browser Unit Tests
Please ensure your test framework is generating JUnit XML output.
Browser Unit Tests
No JUnit XML files found matching pattern: **/*.junit.xml
Browser Unit Tests
No files found matching pattern: **/*.junit.xml
Node (20) Unit Tests
Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: packages/nextjs/src/client/index.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js This usually indicates a path format mismatch between your coverage tool and the repository.
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 (18) Unit Tests
Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: packages/nextjs/src/client/index.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js This usually indicates a path format mismatch between your coverage tool and the repository.
Node (24) Unit Tests
Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: packages/nextjs/src/client/index.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js This usually indicates a path format mismatch between your coverage tool and the repository.
E2E nextjs-sourcemaps Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-userfeedback Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-bun Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-trailing-slash (latest, turbopack) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-trailing-slash Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E node-exports-test-app Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-cacheComponents Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-tunnel Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-cf-workers Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-pages-dir (next@13) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-cf-workers (latest) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-cf-workers (canary) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-tunnel (turbopack) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-orpc Test (optional)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-13 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-13 (latest) Test (optional)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-pages-dir Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-15-basepath Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-15-t3 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-15-intl Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-14 (canary) Test (optional)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16-tunnel (webpack) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-14 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-14 (latest) Test (optional)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-pages-dir (next@15) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-15 (turbo) Test (optional)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-15 (latest) Test (optional)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-15 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16 (latest, turbopack) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-app-dir (next@13) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16 (canary, webpack) Test (optional)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-app-dir Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16 (latest, webpack) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16 (webpack) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-app-dir (next@15) Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E nextjs-16 (canary, turbopack) Test (optional)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
E2E supabase-nextjs Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. 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/
🎭 Playwright Run Summary
12 passed (7.7s)
🎭 Playwright Run Summary
1 skipped 14 passed (11.8s)
🎭 Playwright Run Summary
5 passed (9.9s)
🎭 Playwright Run Summary
5 passed (9.8s)
🎭 Playwright Run Summary
4 passed (18.1s)
🎭 Playwright Run Summary
4 passed (3.6s)
🎭 Playwright Run Summary
3 passed (17.5s)
🎭 Playwright Run Summary
3 passed (11.0s)
🎭 Playwright Run Summary
14 skipped 12 passed (21.4s)
🎭 Playwright Run Summary
4 skipped 10 passed (16.8s)
🎭 Playwright Run Summary
4 skipped 10 passed (5.6s)
🎭 Playwright Run Summary
14 skipped 12 passed (22.0s)
🎭 Playwright Run Summary
14 skipped 12 passed (21.5s)
🎭 Playwright Run Summary
3 passed (15.2s)
🎭 Playwright Run Summary
3 passed (9.7s)
🎭 Playwright Run Summary
3 passed (37.2s)
🎭 Playwright Run Summary
3 passed (7.5s)
🎭 Playwright Run Summary
3 skipped 27 passed (38.5s)
🎭 Playwright Run Summary
30 passed (16.3s)
🎭 Playwright Run Summary
3 skipped 27 passed (39.4s)
🎭 Playwright Run Summary
30 passed (13.7s)
🎭 Playwright Run Summary
4 skipped 10 passed (29.9s)
🎭 Playwright Run Summary
2 skipped 12 passed (7.8s)
🎭 Playwright Run Summary
5 passed (41.5s)
🎭 Playwright Run Summary
5 passed (10.4s)
🎭 Playwright Run Summary
3 passed (35.1s)
🎭 Playwright Run Summary
3 passed (4.2s)
🎭 Playwright Run Summary
4 passed (29.1s)
🎭 Playwright Run Summary
4 passed (6.9s)
🎭 Playwright Run Summary
13 passed (49.9s)
🎭 Playwright Run Summary
13 passed (8.4s)
🎭 Playwright Run Summary
3 passed (37.7s)
🎭 Playwright Run Summary
3 passed (9.7s)
🎭 Playwright Run Summary
13 passed (47.7s)
🎭 Playwright Run Summary
13 passed (9.7s)
🎭 Playwright Run Summary
13 passed (48.5s)
🎭 Playwright Run Summary
13 passed (9.8s)
🎭 Playwright Run Summary
4 skipped 10 passed (32.1s)
🎭 Playwright Run Summary
2 skipped 12 passed (7.9s)
🎭 Playwright Run Summary
2 skipped 29 passed (1.2m)
🎭 Playwright Run Summary
2 skipped 29 passed (36.9s)
🎭 Playwright Run Summary
5 skipped 36 passed (1.7m)
🎭 Playwright Run Summary
2 skipped 39 passed (1.0m)
🎭 Playwright Run Summary
2 skipped 29 passed (1.9m)
🎭 Playwright Run Summary
2 skipped 29 passed (36.9s)
🎭 Playwright Run Summary
2 skipped 29 passed (1.9m)
🎭 Playwright Run Summary
2 skipped 29 passed (36.1s)
🎭 Playwright Run Summary
5 skipped 36 passed (1.7m)
🎭 Playwright Run Summary
2 skipped 39 passed (1.2m)
🎭 Playwright Run Summary
5 skipped 29 passed (1.8m)
🎭 Playwright Run Summary
6 skipped 28 passed (1.0m)
🎭 Playwright Run Summary
7 skipped 34 passed (2.8m)
🎭 Playwright Run Summary
2 skipped 39 passed (1.0m)
🎭 Playwright Run Summary
2 skipped 32 passed (2.5m)
🎭 Playwright Run Summary
2 skipped 32 passed (1.1m)
🎭 Playwright Run Summary
7 skipped 34 passed (2.5m)
🎭 Playwright Run Summary
2 skipped 39 passed (59.5s)
🎭 Playwright Run Summary
7 skipped 34 passed (2.9m)
🎭 Playwright Run Summary
2 skipped 39 passed (1.0m)
🎭 Playwright Run Summary
2 skipped 32 passed (2.9m)
🎭 Playwright Run Summary
2 skipped 32 passed (1.1m)
🎭 Playwright Run Summary
1 failed [chromium] β€Ί tests/server-components.test.ts:4:5 β€Ί Sends a transaction for a request to app router with URL 5 skipped 35 passed (3.8m)
🎭 Playwright Run Summary
2 skipped 39 passed (1.1m)
🎭 Playwright Run Summary
4 passed (18.5s)

Artifacts

Produced during runtime
Name Size Digest
E2E Test Dump (nextjs-16 (canary, turbopack)) Expired
305 KB
sha256:73a761a69cdf478146ce67e3f8eb8c024349154d6d1cca1f7c6befc721b38a45
build-output Expired
33.6 MB
sha256:18df560dfa1015bf6aceb190af666e27822e101c7104048082258958dd75a9d3
codecov-coverage-results-lms-feat-nextjs-client-event-processor-migration-job_browser_unit_tests
1 KB
sha256:8123df94a7e8e542335ebb5dc88fb4f0d72da0fe87decba23d88b3e03b7e6d0a
codecov-coverage-results-lms-feat-nextjs-client-event-processor-migration-job_node_unit_tests-18
1.01 KB
sha256:1f7809fa7df04b591bc8103a7464d25137f9edd8c960b2209b7227665843a325
codecov-coverage-results-lms-feat-nextjs-client-event-processor-migration-job_node_unit_tests-20
1.01 KB
sha256:617ea0d840aef95506571c9acfba3c5f4d7519e5533b21c5602fda4bc07830b7
codecov-coverage-results-lms-feat-nextjs-client-event-processor-migration-job_node_unit_tests-22
1.01 KB
sha256:f953ee15042c6ad7284a951c78b5eb357c99734351c9428c1330d619d45483d6
codecov-coverage-results-lms-feat-nextjs-client-event-processor-migration-job_node_unit_tests-24
1.01 KB
sha256:24cb028f62f9fc695d3d14972ce8868ab2431a4d7d5030c31a0b615b88f8c9ee
codecov-test-results-lms-feat-nextjs-client-event-processor-migration-job_node_unit_tests-18
1.36 KB
sha256:4cab78461214aab2cb44e560c3bc2f59eb9b15dbcfeca20d4573ad84a0c7eb96
codecov-test-results-lms-feat-nextjs-client-event-processor-migration-job_node_unit_tests-20
1.36 KB
sha256:5ca40d8321b7c0ef6ce087adec0d965a311795c5ef3edfa1cc5f28d242c0c92a
codecov-test-results-lms-feat-nextjs-client-event-processor-migration-job_node_unit_tests-22
1.36 KB
sha256:d91ab3b37bec75ed1835a4dec4f9176a60c9ad0ddbbee8c7407745d6ba9749e8
codecov-test-results-lms-feat-nextjs-client-event-processor-migration-job_node_unit_tests-24
1.36 KB
sha256:006bd443be79f47023446b05c1f53d7625005b62b04e3021d16b3fb8fa663486