Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Type 'TSchema' does not satisfy the constraint '{ [key: string]: any; }'.

Type 'TSchema' does not satisfy the constraint '{ [key: string]: any; }'.

Type 'TSchema' does not satisfy the constraint '{ [key: string]: any; }'.

Type 'TSchema' does not satisfy the constraint '{ [key: string]: any; }'.

Property 'inspect' does not exist on type 'typeof import("/__w/sentry-javascript/sentry-javascript/node_modules/@types/ember__debug/index")'.

Subsequent property declarations must have the same type. Property 'onloadingerror' must be of type '((this: FontFaceSet, ev: FontFaceSetLoadEvent) => any) | null', but here has type '((this: FontFaceSet, event: Event) => any) | null'.

Subsequent property declarations must have the same type. Property 'onloadingdone' must be of type '((this: FontFaceSet, ev: FontFaceSetLoadEvent) => any) | null', but here has type '((this: FontFaceSet, event: Event) => any) | null'.

Subsequent property declarations must have the same type. Property 'onloading' must be of type '((this: FontFaceSet, ev: FontFaceSetLoadEvent) => any) | null', but here has type '((this: FontFaceSet, event: Event) => any) | null'.

Subsequent property declarations must have the same type. Property 'display' must be of type 'FontDisplay', but here has type 'string'.

Subsequent property declarations must have the same type. Property 'display' must be of type 'FontDisplay | undefined', but here has type 'string | undefined'.

Process completed with exit code 1.

Process completed with exit code 1.

8) [chromium] › tests/transactions.test.ts:128:5 › Isolates requests ───────────────────────────── TypeError: fetch failed 140 | }); 141 | > 142 | await Promise.all([fetch(`${baseURL}/test-param/888`), fetch(`${baseURL}/test-param/999`)]); | ^ 143 | 144 | const transaction1 = await transaction1Promise; 145 | const transaction2 = await transaction2Promise; at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/transactions.test.ts:142:3 [cause]: Error: connect ECONNREFUSED 127.0.0.1:3030

7) [chromium] › tests/transactions.test.ts:111:5 › Sends parameterized transactions to Sentry ──── TypeError: fetch failed 117 | }); 118 | > 119 | await fetch(`${baseURL}/test-param/123`); | ^ 120 | 121 | const transactionEvent = await pageloadTransactionEventPromise; 122 | at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/transactions.test.ts:119:3 [cause]: Error: connect ECONNREFUSED 127.0.0.1:3030

6) [chromium] › tests/transactions.test.ts:4:5 › Sends successful transaction ──────────────────── TypeError: fetch failed 9 | }); 10 | > 11 | await fetch(`${baseURL}/test-success`); | ^ 12 | 13 | const transactionEvent = await pageloadTransactionEventPromise; 14 | at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/transactions.test.ts:11:3 [cause]: Error: connect ECONNREFUSED 127.0.0.1:3030

5) [chromium] › tests/errors.test.ts:121:5 › Only sends onPreResponse error to Sentry if JS error is thrown in route handler AND onPreResponse TypeError: fetch failed 142 | }); 143 | > 144 | const response = await fetch(`${baseURL}/test-failure-JS-error-onPreResponse`); | ^ 145 | 146 | expect(response.status).toBe(500); 147 | at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/errors.test.ts:144:20 [cause]: Error: connect ECONNREFUSED 127.0.0.1:3030

4) [chromium] › tests/errors.test.ts:96:5 › Does not send error to Sentry if error response is overwritten with 2xx in "onPreResponse" TypeError: fetch failed 110 | }); 111 | > 112 | const response = await fetch(`${baseURL}/test-failure-2xx-override-onPreResponse`); | ^ 113 | 114 | const transactionEvent = await transactionEventPromise; 115 | at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/errors.test.ts:112:20 [cause]: Error: connect ECONNREFUSED 127.0.0.1:3030

3) [chromium] › tests/errors.test.ts:62:5 › Does not send errors to Sentry if boom throws in "onPreResponse" after JS error in route handler TypeError: fetch failed 80 | }); 81 | > 82 | const response4xx = await fetch(`${baseURL}/test-failure-boom-4xx`); | ^ 83 | const response5xx = await fetch(`${baseURL}/test-failure-boom-5xx`); 84 | 85 | expect(response4xx.status).toBe(400); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/errors.test.ts:82:23 [cause]: Error: connect ECONNREFUSED 127.0.0.1:3030

2) [chromium] › tests/errors.test.ts:50:5 › sends error with parameterized transaction name ────── TypeError: fetch failed 53 | }); 54 | > 55 | await fetch(`${baseURL}/test-error/123`); | ^ 56 | 57 | const errorEvent = await errorEventPromise; 58 | at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/errors.test.ts:55:3 [cause]: Error: connect ECONNREFUSED 127.0.0.1:3030

1) [chromium] › tests/errors.test.ts:4:5 › Sends thrown error to Sentry ────────────────────────── TypeError: fetch failed 11 | }); 12 | > 13 | await fetch(`${baseURL}/test-failure`); | ^ 14 | 15 | const errorEvent = await errorEventPromise; 16 | const transactionEvent = await transactionEventPromise; at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/errors.test.ts:13:3 [cause]: Error: connect ECONNREFUSED 127.0.0.1:3030

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Error: Command failed: docker compose down --volumes at ../global-teardown.mjs:9 7 | export default async function globalTeardown() { 8 | // Stop Redis and remove containers > 9 | execSync('docker compose down --volumes', { | ^ 10 | cwd: __dirname, 11 | stdio: 'inherit', 12 | }); at globalTeardown (/__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/global-teardown.mjs:9:3)

Error: Command failed: docker compose up -d --wait at ../global-setup.mjs:9 7 | export default async function globalSetup() { 8 | // Start Redis via Docker Compose > 9 | execSync('docker compose up -d --wait', { | ^ 10 | cwd: __dirname, 11 | stdio: 'inherit', 12 | }); at globalSetup (/__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/global-setup.mjs:9:3)

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

1) [chromium] › tests/index.test.ts:13:5 › Worker and Durable Object both send transactions when worker calls DO Test timeout of 30000ms exceeded.

Process completed with exit code 1.

1) [chromium] › tests/index.test.ts:4:5 › sends spans for MCP tool calls ───────────────────────── Test timeout of 30000ms exceeded.

Process completed with exit code 1.

Process completed with exit code 1.

2) [chromium] › tests/tracing.dynamic.test.ts:178:3 › nested SSR routes (client, server, server request) › sends parametrized pageload, server and API request transaction names Test timeout of 30000ms exceeded.

1) [chromium] › tests/tracing.dynamic.test.ts:137:3 › nested SSR routes (client, server, server request) › sends connected server and client pageload and request spans with the same trace id Test timeout of 30000ms exceeded.

Process completed with exit code 1.

1) [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it Error: expect(received).toEqual(expected) // deep equality Expected: ArrayContaining [{"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "::1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": StringMatching /[a-f0-9]{16}/, "span_id": StringMatching /[a-f0-9]{16}/, "start_timestamp": Any<Number>, "status": "ok", "timestamp": Any<Number>, "trace_id": StringMatching /[a-f0-9]{32}/}] Received: [{"data": {"http.method": "GET", "http.target": "/api/endpoint-behind-middleware", "next.span_name": "middleware GET", "next.span_type": "Middleware.execute", "sentry.op": "http", "sentry.origin": "auto"}, "description": "GET /api/endpoint-behind-middleware", "op": "http", "origin": "auto", "parent_span_id": "09682697cbdd352f", "span_id": "a71854cf7fa36ef5", "start_timestamp": 1776411685.591, "status": "ok", "timestamp": 1776411685.6149836, "trace_id": "927a06a199ae1d805c4210afb68b52e6"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "127.0.0.1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "a71854cf7fa36ef5", "span_id": "edc5a734a2ba648e", "start_timestamp": 1776411685.597, "status": "ok", "timestamp": 1776411685.6133955, "trace_id": "927a06a199ae1d805c4210afb68b52e6"}] 98 | if (hasHttpClientSpan) { 99 | // Check if fetch is traced as a child span of the middleware transaction > 100 | expect(middlewareTransaction.spans).toEqual( | ^ 101 | expect.arrayContaining([ 102 | { 103 | data: { at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/middleware.test.ts:100:41

Process completed with exit code 1.

Process completed with exit code 1.

2) [chromium] › tests/tracing.dynamic.test.ts:175:3 › nested SSR routes (client, server, server request) › sends parametrized pageload, server and API request transaction names Test timeout of 30000ms exceeded.

1) [chromium] › tests/tracing.dynamic.test.ts:134:3 › nested SSR routes (client, server, server request) › sends connected server and client pageload and request spans with the same trace id Test timeout of 30000ms exceeded.

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.

1) [chromium] › tests/orpc-error.test.ts:4:1 › should capture server-side orpc error ───────────── Error: page.goto: Test timeout of 30000ms exceeded. Call log: - navigating to "http://localhost:3030/", waiting until "load" 10 | }); 11 | > 12 | await page.goto('/'); | ^ 13 | await page.waitForTimeout(500); 14 | await page.getByRole('link', { name: 'Error' }).click(); 15 | at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/orpc-error.test.ts:12:14

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

Process completed with exit code 1.

1) [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it Error: expect(received).toEqual(expected) // deep equality Expected: ArrayContaining [{"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "::1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": StringMatching /[a-f0-9]{16}/, "span_id": StringMatching /[a-f0-9]{16}/, "start_timestamp": Any<Number>, "status": "ok", "timestamp": Any<Number>, "trace_id": StringMatching /[a-f0-9]{32}/}] Received: [{"data": {"http.method": "GET", "http.target": "/api/endpoint-behind-middleware", "next.span_name": "middleware GET", "next.span_type": "Middleware.execute", "sentry.op": "http", "sentry.origin": "auto"}, "description": "GET /api/endpoint-behind-middleware", "op": "http", "origin": "auto", "parent_span_id": "ce9ec43d750aeaa6", "span_id": "ad0be0e219085033", "start_timestamp": 1776411702.006, "status": "ok", "timestamp": 1776411702.029596, "trace_id": "25c8bb3cbf860fdee9427ce62520bce7"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "127.0.0.1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "ad0be0e219085033", "span_id": "e2eeac5ce8b52bbf", "start_timestamp": 1776411702.011, "status": "ok", "timestamp": 1776411702.0269513, "trace_id": "25c8bb3cbf860fdee9427ce62520bce7"}] 98 | if (hasHttpClientSpan) { 99 | // Check if fetch is traced as a child span of the middleware transaction > 100 | expect(middlewareTransaction.spans).toEqual( | ^ 101 | expect.arrayContaining([ 102 | { 103 | data: { at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/middleware.test.ts:100:41

Process completed with exit code 1.

1) [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it Error: expect(received).toEqual(expected) // deep equality Expected: ArrayContaining [{"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "::1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": StringMatching /[a-f0-9]{16}/, "span_id": StringMatching /[a-f0-9]{16}/, "start_timestamp": Any<Number>, "status": "ok", "timestamp": Any<Number>, "trace_id": StringMatching /[a-f0-9]{32}/}] Received: [{"data": {"http.method": "GET", "http.target": "/api/endpoint-behind-middleware", "next.span_name": "middleware GET", "next.span_type": "Middleware.execute", "sentry.op": "http", "sentry.origin": "auto"}, "description": "GET /api/endpoint-behind-middleware", "op": "http", "origin": "auto", "parent_span_id": "1bfd7bc40edf2e5c", "span_id": "94b2f0d219f61c4f", "start_timestamp": 1776411713.177, "status": "ok", "timestamp": 1776411713.1999884, "trace_id": "dae5079fe51a8062c3265df92cb62e15"}, {"data": {"sentry.op": "http.server.middleware", "sentry.origin": "auto.function.nextjs.wrap_middleware", "sentry.source": "component"}, "description": "middleware", "op": "http.server.middleware", "origin": "auto.function.nextjs.wrap_middleware", "parent_span_id": "94b2f0d219f61c4f", "span_id": "6424cace1337a547", "start_timestamp": 1776411713.177, "status": "ok", "timestamp": 1776411713.1988873, "trace_id": "dae5079fe51a8062c3265df92cb62e15"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "127.0.0.1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "6424cace1337a547", "span_id": "b5f0126358c8f4f4", "start_timestamp": 1776411713.183, "status": "ok", "timestamp": 1776411713.1972148, "trace_id": "dae5079fe51a8062c3265df92cb62e15"}] 98 | if (hasHttpClientSpan) { 99 | // Check if fetch is traced as a child span of the middleware transaction > 100 | expect(middlewareTransaction.spans).toEqual( | ^ 101 | expect.arrayContaining([ 102 | { 103 | data: { at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/middleware.test.ts:100:41

Process completed with exit code 1.

1) [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it Error: expect(received).toEqual(expected) // deep equality Expected: ArrayContaining [{"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "::1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": StringMatching /[a-f0-9]{16}/, "span_id": StringMatching /[a-f0-9]{16}/, "start_timestamp": Any<Number>, "status": "ok", "timestamp": Any<Number>, "trace_id": StringMatching /[a-f0-9]{32}/}] Received: [{"data": {"http.method": "GET", "http.target": "/api/endpoint-behind-middleware", "next.span_name": "middleware GET", "next.span_type": "Middleware.execute", "sentry.op": "http", "sentry.origin": "auto"}, "description": "GET /api/endpoint-behind-middleware", "op": "http", "origin": "auto", "parent_span_id": "c7efb9f840aedac5", "span_id": "568abd32d240ef0c", "start_timestamp": 1776411715.954, "status": "ok", "timestamp": 1776411715.9937515, "trace_id": "a7f65c41d9e16a7dbd3d478670878828"}, {"data": {"sentry.op": "http.server.middleware", "sentry.origin": "auto.function.nextjs.wrap_middleware", "sentry.source": "component"}, "description": "middleware", "op": "http.server.middleware", "origin": "auto.function.nextjs.wrap_middleware", "parent_span_id": "568abd32d240ef0c", "span_id": "181bf150a9f8303d", "start_timestamp": 1776411715.955, "status": "ok", "timestamp": 1776411715.993469, "trace_id": "a7f65c41d9e16a7dbd3d478670878828"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "127.0.0.1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "181bf150a9f8303d", "span_id": "2dadefda62b6264c", "start_timestamp": 1776411715.96, "status": "ok", "timestamp": 1776411715.9902046, "trace_id": "a7f65c41d9e16a7dbd3d478670878828"}] 98 | if (hasHttpClientSpan) { 99 | // Check if fetch is traced as a child span of the middleware transaction > 100 | expect(middlewareTransaction.spans).toEqual( | ^ 101 | expect.arrayContaining([ 102 | { 103 | data: { at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/middleware.test.ts:100:41

Process completed with exit code 1.

1) [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it Error: expect(received).toEqual(expected) // deep equality Expected: ArrayContaining [{"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "::1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": StringMatching /[a-f0-9]{16}/, "span_id": StringMatching /[a-f0-9]{16}/, "start_timestamp": Any<Number>, "status": "ok", "timestamp": Any<Number>, "trace_id": StringMatching /[a-f0-9]{32}/}] Received: [{"data": {"http.method": "GET", "http.target": "/api/endpoint-behind-middleware", "next.span_name": "middleware GET", "next.span_type": "Middleware.execute", "sentry.op": "http", "sentry.origin": "auto"}, "description": "GET /api/endpoint-behind-middleware", "op": "http", "origin": "auto", "parent_span_id": "74cc75b512f6a5f1", "span_id": "efb5b04ad9430bd6", "start_timestamp": 1776411732.514, "status": "ok", "timestamp": 1776411732.536764, "trace_id": "e3cc010b1c7993da3d96f1842fc7161c"}, {"data": {"sentry.op": "http.server.middleware", "sentry.origin": "auto.function.nextjs.wrap_middleware", "sentry.source": "component"}, "description": "middleware", "op": "http.server.middleware", "origin": "auto.function.nextjs.wrap_middleware", "parent_span_id": "efb5b04ad9430bd6", "span_id": "38edc0892d293b3b", "start_timestamp": 1776411732.514, "status": "ok", "timestamp": 1776411732.5356147, "trace_id": "e3cc010b1c7993da3d96f1842fc7161c"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "127.0.0.1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "38edc0892d293b3b", "span_id": "bda1fb1e1f3b717a", "start_timestamp": 1776411732.52, "status": "ok", "timestamp": 1776411732.5339243, "trace_id": "e3cc010b1c7993da3d96f1842fc7161c"}] 98 | if (hasHttpClientSpan) { 99 | // Check if fetch is traced as a child span of the middleware transaction > 100 | expect(middlewareTransaction.spans).toEqual( | ^ 101 | expect.arrayContaining([ 102 | { 103 | data: { at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/middleware.test.ts:100:41

Process completed with exit code 1.

1) [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it Error: expect(received).toEqual(expected) // deep equality Expected: ArrayContaining [{"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "::1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": StringMatching /[a-f0-9]{16}/, "span_id": StringMatching /[a-f0-9]{16}/, "start_timestamp": Any<Number>, "status": "ok", "timestamp": Any<Number>, "trace_id": StringMatching /[a-f0-9]{32}/}] Received: [{"data": {"http.method": "GET", "http.target": "/api/endpoint-behind-middleware", "next.span_name": "middleware GET", "next.span_type": "Middleware.execute", "sentry.op": "http", "sentry.origin": "auto"}, "description": "GET /api/endpoint-behind-middleware", "op": "http", "origin": "auto", "parent_span_id": "a3f114fcdd08115a", "span_id": "3e102c26e516cb3d", "start_timestamp": 1776411738.76, "status": "ok", "timestamp": 1776411738.777503, "trace_id": "c150f8c02be11e76f8b9c624c35b3a20"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "127.0.0.1", "network.peer.port": 3030, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "localhost", "server.port": 3030, "url": "http://localhost:3030/", "url.full": "http://localhost:3030/", "url.path": "/", "url.query": "", "url.scheme": "http", "user_agent.original": "node"}, "description": "GET http://localhost:3030/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "3e102c26e516cb3d", "span_id": "2d6b982c089573f7", "start_timestamp": 1776411738.764, "status": "ok", "timestamp": 1776411738.7756941, "trace_id": "c150f8c02be11e76f8b9c624c35b3a20"}] 98 | if (hasHttpClientSpan) { 99 | // Check if fetch is traced as a child span of the middleware transaction > 100 | expect(middlewareTransaction.spans).toEqual( | ^ 101 | expect.arrayContaining([ 102 | { 103 | data: { at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/middleware.test.ts:100:41

Process completed with exit code 1.

5) [chromium] › tests/server-transactions.test.ts:20:1 › Sends two linked transactions (server & client) to Sentry Test timeout of 30000ms exceeded.

4) [chromium] › tests/client-transactions.test.ts:16:1 › Sends a navigation transaction to Sentry Test timeout of 30000ms exceeded.

3) [chromium] › tests/client-transactions.test.ts:4:1 › Sends a pageload transaction to Sentry ─── Test timeout of 30000ms exceeded.

2) [chromium] › tests/client-errors.test.ts:19:1 › Sends a client-side ErrorBoundary exception to Sentry Test timeout of 30000ms exceeded.

1) [chromium] › tests/client-errors.test.ts:4:1 › Sends a client-side exception to Sentry ──────── Test timeout of 30000ms exceeded.

Process completed with exit code 1.

5) [chromium] › tests/server-transactions.test.ts:19:1 › Sends two linked transactions (server & client) to Sentry Test timeout of 30000ms exceeded.

4) [chromium] › tests/client-transactions.test.ts:16:1 › Sends a navigation transaction to Sentry Test timeout of 30000ms exceeded.

3) [chromium] › tests/client-transactions.test.ts:4:1 › Sends a pageload transaction to Sentry ─── Test timeout of 30000ms exceeded.

2) [chromium] › tests/client-errors.test.ts:19:1 › Sends a client-side ErrorBoundary exception to Sentry Test timeout of 30000ms exceeded.

1) [chromium] › tests/client-errors.test.ts:4:1 › Sends a client-side exception to Sentry ──────── Test timeout of 30000ms exceeded.

Process completed with exit code 1.

8) [chromium] › tests/index.test.ts:86:5 › Storage operations create spans in Durable Object transactions Test timeout of 30000ms exceeded.

7) [chromium] › tests/index.test.ts:74:5 › sends user-agent header with SDK name and version in envelope requests Test timeout of 30000ms exceeded.

6) [chromium] › tests/index.test.ts:58:5 › Websocket.webSocketClose ────────────────────────────── Test timeout of 30000ms exceeded.

5) [chromium] › tests/index.test.ts:42:5 › Websocket.webSocketMessage ──────────────────────────── Test timeout of 30000ms exceeded.

4) [chromium] › tests/index.test.ts:32:5 › Request processed by DurableObject's fetch is recorded Test timeout of 30000ms exceeded.

3) [chromium] › tests/index.test.ts:22:5 › RPC method which throws an exception to be logged to sentry Test timeout of 30000ms exceeded.

2) [chromium] › tests/index.test.ts:12:5 › worker's withSentry ─────────────────────────────────── Test timeout of 30000ms exceeded.

1) [chromium] › tests/index.test.ts:6:5 › Index page ───────────────────────────────────────────── Test timeout of 30000ms exceeded.

7) [chromium] › tests/errors.server.test.ts:126:3 › server-side errors › captures API route error Test timeout of 30000ms exceeded.

6) [chromium] › tests/errors.server.test.ts:72:3 › server-side errors › captures endpoint error ── Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/endpoint-error", waiting until "load" 81 | }); 82 | > 83 | await page.goto('/endpoint-error'); | ^ 84 | await page.getByText('Get Data').click(); 85 | 86 | const errorEvent = await errorEventPromise; at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/errors.server.test.ts:83:16

6) [chromium] › tests/errors.server.test.ts:72:3 › server-side errors › captures endpoint error ── Test timeout of 30000ms exceeded.

5) [chromium] › tests/errors.server.test.ts:5:3 › server-side errors › captures SSR error ──────── Test timeout of 30000ms exceeded.

4) [chromium] › tests/cloudflare-runtime.test.ts:30:3 › Cloudflare Runtime › Should report cloudflare as the runtime in API route error events Test timeout of 30000ms exceeded.

3) [chromium] › tests/cloudflare-runtime.test.ts:5:3 › Cloudflare Runtime › Should report cloudflare as the runtime in SSR error events Test timeout of 30000ms exceeded.

2) [chromium] › tests/actions.test.ts:22:3 › Astro actions › action submission creates a transaction Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/action-test", waiting until "load" 21 | 22 | test('action submission creates a transaction', async ({ page }) => { > 23 | await page.goto('/action-test'); | ^ 24 | 25 | const transactionEventPromise = waitForTransaction('astro-5-cf-workers', transactionEvent => { 26 | return ( at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/actions.test.ts:23:16

2) [chromium] › tests/actions.test.ts:22:3 › Astro actions › action submission creates a transaction Test timeout of 30000ms exceeded.

1) [chromium] › tests/actions.test.ts:5:3 › Astro actions › captures transaction for action call ─ Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/action-test", waiting until "load" 8 | }); 9 | > 10 | await page.goto('/action-test'); | ^ 11 | 12 | const transactionEvent = await transactionEventPromise; 13 | at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/actions.test.ts:10:16

1) [chromium] › tests/actions.test.ts:5:3 › Astro actions › captures transaction for action call ─ Test timeout of 30000ms exceeded.

Process completed with exit code 1.

9) [chromium] › tests/index.test.ts:106:7 › Alarm instrumentation › captures error from alarm handler Test timeout of 30000ms exceeded.

8) [chromium] › tests/index.test.ts:86:5 › Storage operations create spans in Durable Object transactions Test timeout of 30000ms exceeded.

7) [chromium] › tests/index.test.ts:74:5 › sends user-agent header with SDK name and version in envelope requests Test timeout of 30000ms exceeded.

6) [chromium] › tests/index.test.ts:58:5 › Websocket.webSocketClose ────────────────────────────── Test timeout of 30000ms exceeded.

5) [chromium] › tests/index.test.ts:42:5 › Websocket.webSocketMessage ──────────────────────────── Test timeout of 30000ms exceeded.

4) [chromium] › tests/index.test.ts:32:5 › Request processed by DurableObject's fetch is recorded Test timeout of 30000ms exceeded.

3) [chromium] › tests/index.test.ts:22:5 › RPC method which throws an exception to be logged to sentry Test timeout of 30000ms exceeded.

2) [chromium] › tests/index.test.ts:12:5 › worker's withSentry ─────────────────────────────────── Test timeout of 30000ms exceeded.

1) [chromium] › tests/index.test.ts:6:5 › Index page ───────────────────────────────────────────── Test timeout of 30000ms exceeded.

6) [chromium] › tests/isr-routes.test.ts:74:5 › ISR route should be identified correctly in the route manifest Test timeout of 30000ms exceeded.

5) [chromium] › tests/isr-routes.test.ts:44:5 › should create unique transactions for ISR pages on each visit Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/laptop", waiting until "load" 54 | 55 | if (i === 0) { > 56 | await page.goto('/isr-test/laptop'); | ^ 57 | } else { 58 | await page.reload(); 59 | } at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:56:18

5) [chromium] › tests/isr-routes.test.ts:44:5 › should create unique transactions for ISR pages on each visit Test timeout of 30000ms exceeded.

4) [chromium] › tests/isr-routes.test.ts:28:5 › should remove meta tags for different ISR dynamic route values Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/phone", waiting until "load" 28 | test('should remove meta tags for different ISR dynamic route values', async ({ page }) => { 29 | // Test with 'phone' (one of the pre-generated static params) > 30 | await page.goto('/isr-test/phone'); | ^ 31 | await expect(page.locator('#isr-product-id')).toHaveText('phone'); 32 | 33 | await expect(page.locator('meta[name="sentry-trace"]')).toHaveCount(0); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:30:14

4) [chromium] › tests/isr-routes.test.ts:28:5 › should remove meta tags for different ISR dynamic route values Test timeout of 30000ms exceeded.

3) [chromium] › tests/isr-routes.test.ts:16:5 › should remove sentry-trace and baggage meta tags on ISR static route Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/static", waiting until "load" 16 | test('should remove sentry-trace and baggage meta tags on ISR static route', async ({ page }) => { 17 | // Navigate to ISR static page > 18 | await page.goto('/isr-test/static'); | ^ 19 | 20 | // Wait for page to be fully loaded 21 | await expect(page.locator('#isr-static-marker')).toHaveText('static-isr'); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:18:14

3) [chromium] › tests/isr-routes.test.ts:16:5 › should remove sentry-trace and baggage meta tags on ISR static route Test timeout of 30000ms exceeded.

2) [chromium] › tests/isr-routes.test.ts:4:5 › should remove sentry-trace and baggage meta tags on ISR dynamic route page load Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/laptop", waiting until "load" 4 | test('should remove sentry-trace and baggage meta tags on ISR dynamic route page load', async ({ page }) => { 5 | // Navigate to ISR page > 6 | await page.goto('/isr-test/laptop'); | ^ 7 | 8 | // Wait for page to be fully loaded 9 | await expect(page.locator('#isr-product-id')).toHaveText('laptop'); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:6:14

2) [chromium] › tests/isr-routes.test.ts:4:5 › should remove sentry-trace and baggage meta tags on ISR dynamic route page load Test timeout of 30000ms exceeded.

1) [chromium] › tests/cloudflare-runtime.test.ts:5:7 › Cloudflare Runtime › Should report cloudflare as the runtime in API route error events Test timeout of 30000ms exceeded.

6) [chromium] › tests/isr-routes.test.ts:74:5 › ISR route should be identified correctly in the route manifest Test timeout of 30000ms exceeded.

5) [chromium] › tests/isr-routes.test.ts:44:5 › should create unique transactions for ISR pages on each visit Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/laptop", waiting until "load" 54 | 55 | if (i === 0) { > 56 | await page.goto('/isr-test/laptop'); | ^ 57 | } else { 58 | await page.reload(); 59 | } at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:56:18

5) [chromium] › tests/isr-routes.test.ts:44:5 › should create unique transactions for ISR pages on each visit Test timeout of 30000ms exceeded.

4) [chromium] › tests/isr-routes.test.ts:28:5 › should remove meta tags for different ISR dynamic route values Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/phone", waiting until "load" 28 | test('should remove meta tags for different ISR dynamic route values', async ({ page }) => { 29 | // Test with 'phone' (one of the pre-generated static params) > 30 | await page.goto('/isr-test/phone'); | ^ 31 | await expect(page.locator('#isr-product-id')).toHaveText('phone'); 32 | 33 | await expect(page.locator('meta[name="sentry-trace"]')).toHaveCount(0); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:30:14

4) [chromium] › tests/isr-routes.test.ts:28:5 › should remove meta tags for different ISR dynamic route values Test timeout of 30000ms exceeded.

3) [chromium] › tests/isr-routes.test.ts:16:5 › should remove sentry-trace and baggage meta tags on ISR static route Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/static", waiting until "load" 16 | test('should remove sentry-trace and baggage meta tags on ISR static route', async ({ page }) => { 17 | // Navigate to ISR static page > 18 | await page.goto('/isr-test/static'); | ^ 19 | 20 | // Wait for page to be fully loaded 21 | await expect(page.locator('#isr-static-marker')).toHaveText('static-isr'); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:18:14

3) [chromium] › tests/isr-routes.test.ts:16:5 › should remove sentry-trace and baggage meta tags on ISR static route Test timeout of 30000ms exceeded.

2) [chromium] › tests/isr-routes.test.ts:4:5 › should remove sentry-trace and baggage meta tags on ISR dynamic route page load Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/laptop", waiting until "load" 4 | test('should remove sentry-trace and baggage meta tags on ISR dynamic route page load', async ({ page }) => { 5 | // Navigate to ISR page > 6 | await page.goto('/isr-test/laptop'); | ^ 7 | 8 | // Wait for page to be fully loaded 9 | await expect(page.locator('#isr-product-id')).toHaveText('laptop'); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:6:14

2) [chromium] › tests/isr-routes.test.ts:4:5 › should remove sentry-trace and baggage meta tags on ISR dynamic route page load Test timeout of 30000ms exceeded.

1) [chromium] › tests/cloudflare-runtime.test.ts:5:7 › Cloudflare Runtime › Should report cloudflare as the runtime in API route error events Test timeout of 30000ms exceeded.

6) [chromium] › tests/isr-routes.test.ts:74:5 › ISR route should be identified correctly in the route manifest Test timeout of 30000ms exceeded.

5) [chromium] › tests/isr-routes.test.ts:44:5 › should create unique transactions for ISR pages on each visit Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/laptop", waiting until "load" 54 | 55 | if (i === 0) { > 56 | await page.goto('/isr-test/laptop'); | ^ 57 | } else { 58 | await page.reload(); 59 | } at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:56:18

5) [chromium] › tests/isr-routes.test.ts:44:5 › should create unique transactions for ISR pages on each visit Test timeout of 30000ms exceeded.

4) [chromium] › tests/isr-routes.test.ts:28:5 › should remove meta tags for different ISR dynamic route values Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/phone", waiting until "load" 28 | test('should remove meta tags for different ISR dynamic route values', async ({ page }) => { 29 | // Test with 'phone' (one of the pre-generated static params) > 30 | await page.goto('/isr-test/phone'); | ^ 31 | await expect(page.locator('#isr-product-id')).toHaveText('phone'); 32 | 33 | await expect(page.locator('meta[name="sentry-trace"]')).toHaveCount(0); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:30:14

4) [chromium] › tests/isr-routes.test.ts:28:5 › should remove meta tags for different ISR dynamic route values Test timeout of 30000ms exceeded.

3) [chromium] › tests/isr-routes.test.ts:16:5 › should remove sentry-trace and baggage meta tags on ISR static route Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/static", waiting until "load" 16 | test('should remove sentry-trace and baggage meta tags on ISR static route', async ({ page }) => { 17 | // Navigate to ISR static page > 18 | await page.goto('/isr-test/static'); | ^ 19 | 20 | // Wait for page to be fully loaded 21 | await expect(page.locator('#isr-static-marker')).toHaveText('static-isr'); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:18:14

3) [chromium] › tests/isr-routes.test.ts:16:5 › should remove sentry-trace and baggage meta tags on ISR static route Test timeout of 30000ms exceeded.

2) [chromium] › tests/isr-routes.test.ts:4:5 › should remove sentry-trace and baggage meta tags on ISR dynamic route page load Error: page.goto: net::ERR_ABORTED; maybe frame was detached? Call log: - navigating to "http://localhost:3030/isr-test/laptop", waiting until "load" 4 | test('should remove sentry-trace and baggage meta tags on ISR dynamic route page load', async ({ page }) => { 5 | // Navigate to ISR page > 6 | await page.goto('/isr-test/laptop'); | ^ 7 | 8 | // Wait for page to be fully loaded 9 | await expect(page.locator('#isr-product-id')).toHaveText('laptop'); at /__w/sentry-javascript/sentry-javascript/dev-packages/tmp-test-application/tests/isr-routes.test.ts:6:14

2) [chromium] › tests/isr-routes.test.ts:4:5 › should remove sentry-trace and baggage meta tags on ISR dynamic route page load Test timeout of 30000ms exceeded.

1) [chromium] › tests/cloudflare-runtime.test.ts:5:7 › Cloudflare Runtime › Should report cloudflare as the runtime in API route error events Test timeout of 30000ms exceeded.

The action 'Run E2E test' has timed out after 10 minutes.

The action 'Run E2E test' has timed out after 10 minutes.

The action 'Run E2E test' has timed out after 10 minutes.

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/

Identifier 'beforeEach' is imported but never used.

Identifier 'afterEach' is imported but never used.

Identifier 'vi' is imported but never used.

Identifier 'beforeEach' is imported but never used.

Identifier 'afterEach' is imported but never used.

Identifier 'hasSpanStreamingEnabled' is imported but never used.

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/

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: .github/actions/ensure-playwright-image/action.yml, .github/actions/install-dependencies/action.yml, .github/actions/restore-cache/action.yml, .github/docker/playwright.Dockerfile, .github/workflows/build.yml, .github/workflows/canary.yml, .github/workflows/flaky-test-detector.yml, scripts/dependency-hash-key.js, yarn.lock 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.

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: .github/actions/ensure-playwright-image/action.yml, .github/actions/install-dependencies/action.yml, .github/actions/restore-cache/action.yml, .github/docker/playwright.Dockerfile, .github/workflows/build.yml, .github/workflows/canary.yml, .github/workflows/flaky-test-detector.yml, scripts/dependency-hash-key.js, yarn.lock 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.

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: .github/actions/ensure-playwright-image/action.yml, .github/actions/install-dependencies/action.yml, .github/actions/restore-cache/action.yml, .github/docker/playwright.Dockerfile, .github/workflows/build.yml, .github/workflows/canary.yml, .github/workflows/flaky-test-detector.yml, scripts/dependency-hash-key.js, yarn.lock 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.

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: .github/actions/ensure-playwright-image/action.yml, .github/actions/install-dependencies/action.yml, .github/actions/restore-cache/action.yml, .github/docker/playwright.Dockerfile, .github/workflows/build.yml, .github/workflows/canary.yml, .github/workflows/flaky-test-detector.yml, scripts/dependency-hash-key.js, yarn.lock 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.

❌ Project coverage check failed: 57.06% (-0.01%) relative to base

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: .github/actions/ensure-playwright-image/action.yml, .github/actions/install-dependencies/action.yml, .github/actions/restore-cache/action.yml, .github/docker/playwright.Dockerfile, .github/workflows/build.yml, .github/workflows/canary.yml, .github/workflows/flaky-test-detector.yml, scripts/dependency-hash-key.js, yarn.lock 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: 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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

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/

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/

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/

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/

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/

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, 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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

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/

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, 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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

No files were found with the provided path: dev-packages/tmp-test-application/test-results. No artifacts will be uploaded.

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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, 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/

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, 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/

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, 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/

7 skipped 23 passed (10.0s)

8 skipped 22 passed (9.1s)

5 skipped 25 passed (11.2s)

1 skipped 29 passed (19.1s)

7 skipped 23 passed (9.9s)

5 skipped 25 passed (16.9s)

4 skipped 26 passed (20.4s)

1 skipped 14 passed (24.1s)

470 skipped 195 passed (38.2s)

475 skipped 190 passed (36.5s)

340 skipped 325 passed (1.5m)

338 skipped 327 passed (1.5m)

1 skipped 166 passed (2.4m)

3 skipped 163 passed (2.6m)

244 skipped 421 passed (3.3m)

3 skipped 17 passed (3.5s)

3 passed (3.8s)

4 passed (2.7s)

11 passed (3.1s)

4 passed (5.5s)

4 passed (4.0s)

2 passed (5.2s)

2 passed (5.4s)

1 passed (2.8s)

2 passed (2.9s)

3 passed (4.7s)

4 passed (7.3s)

12 passed (9.3s)

3 passed (3.2s)

5 passed (9.1s)

7 passed (6.8s)

1 passed (5.0s)

3 passed (8.0s)

3 passed (7.5s)

8 failed [chromium] › tests/errors.test.ts:4:5 › Sends thrown error to Sentry ─────────────────────────── [chromium] › tests/errors.test.ts:50:5 › sends error with parameterized transaction name ─────── [chromium] › tests/errors.test.ts:62:5 › Does not send errors to Sentry if boom throws in "onPreResponse" after JS error in route handler [chromium] › tests/errors.test.ts:96:5 › Does not send error to Sentry if error response is overwritten with 2xx in "onPreResponse" [chromium] › tests/errors.test.ts:121:5 › Only sends onPreResponse error to Sentry if JS error is thrown in route handler AND onPreResponse [chromium] › tests/transactions.test.ts:4:5 › Sends successful transaction ───────────────────── [chromium] › tests/transactions.test.ts:111:5 › Sends parameterized transactions to Sentry ───── [chromium] › tests/transactions.test.ts:128:5 › Isolates requests ──────────────────────────────

1 passed (5.4s)

1 passed (7.6s)

1 passed (5.3s)

3 passed (4.3s)

12 passed (7.2s)

1 passed (4.3s)

3 skipped 17 passed (2.9s)

4 passed (3.4s)

3 passed (3.4s)

11 passed (5.8s)

11 passed (6.1s)

2 passed (4.7s)

3 passed (3.7s)

11 passed (7.4s)

11 passed (8.4s)

3 passed (14.3s)

5 passed (8.6s)

3 passed (4.5s)

13 passed (13.0s)

5 passed (8.5s)

4 passed (4.0s)

4 passed (5.2s)

8 passed (6.5s)

23 passed (17.8s)

4 passed (8.1s)

5 passed (9.1s)

10 passed (11.2s)

22 passed (10.0s)

3 passed (9.4s)

18 passed (18.4s)

4 passed (8.5s)

5 passed (19.1s)

9 passed (10.5s)

16 passed (24.0s)

8 passed (7.1s)

2 skipped 19 passed (22.6s)

3 passed (14.5s)

5 passed (8.5s)

3 passed (4.8s)

3 passed (3.5s)

12 passed (8.5s)

9 passed (11.2s)

13 passed (25.3s)

12 passed (7.8s)

29 passed (32.5s)

3 passed (19.8s)

12 passed (27.9s)

4 passed (8.0s)

2 skipped 19 passed (22.7s)

18 passed (19.3s)

12 passed (27.9s)

24 passed (17.5s)

10 passed (6.3s)

10 passed (6.8s)

12 passed (28.4s)

3 passed (6.0s)

16 passed (31.2s)

5 passed (9.8s)

13 passed (29.2s)

5 passed (8.3s)

4 passed (10.9s)

14 passed (25.4s)

3 skipped 21 passed (19.3s)

10 passed (37.2s)

9 passed (11.6s)

4 passed (8.6s)

12 passed (6.6s)

10 passed (27.7s)

4 passed (17.9s)

4 passed (4.3s)

9 passed (11.7s)

12 passed (28.3s)

10 passed (27.4s)

253 skipped 412 passed (4.4m)

3 skipped 163 passed (4.5m)

9 passed (11.6s)

7 passed (8.1s)

3 passed (17.9s)

3 passed (10.4s)

1 skipped 14 passed (13.0s)

8 passed (29.3s)

3 passed (18.2s)

9 passed (12.1s)

3 passed (10.2s)

12 passed (28.6s)

4 passed (11.1s)

7 passed (8.2s)

1 failed [chromium] › tests/index.test.ts:13:5 › Worker and Durable Object both send transactions when worker calls DO

248 skipped 417 passed (4.5m)

5 skipped 161 passed (4.6m)

15 passed (21.1s)

1 failed [chromium] › tests/index.test.ts:4:5 › sends spans for MCP tool calls ──────────────────────────

15 passed (9.5s)

8 passed (30.6s)

10 passed (25.6s)

4 skipped 10 passed (26.6s)

4 skipped 10 passed (6.7s)

117 skipped 548 passed (5.3m)

5 passed (9.0s)

2 failed [chromium] › tests/tracing.dynamic.test.ts:137:3 › nested SSR routes (client, server, server request) › sends connected server and client pageload and request spans with the same trace id [chromium] › tests/tracing.dynamic.test.ts:178:3 › nested SSR routes (client, server, server request) › sends parametrized pageload, server and API request transaction names 9 passed (1.2m)

4 passed (35.3s)

4 passed (7.9s)

12 passed (28.3s)

13 passed (46.9s)

13 passed (8.9s)

3 passed (37.5s)

3 passed (10.0s)

1 failed [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it 2 skipped 38 passed (1.1m)

3 skipped 27 passed (43.2s)

30 passed (12.6s)

2 failed [chromium] › tests/tracing.dynamic.test.ts:134:3 › nested SSR routes (client, server, server request) › sends connected server and client pageload and request spans with the same trace id [chromium] › tests/tracing.dynamic.test.ts:175:3 › nested SSR routes (client, server, server request) › sends parametrized pageload, server and API request transaction names 7 passed (1.2m)

117 skipped 548 passed (5.3m)

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 (39.3s)

3 passed (3.7s)

114 skipped 551 passed (5.2m)

1 flaky [chromium] › tests/orpc-error.test.ts:4:1 › should capture server-side orpc error ────────────── 2 passed (44.6s)

3 passed (7.5s)

3 skipped 27 passed (41.9s)

30 passed (13.2s)

112 skipped 553 passed (5.4m)

1 failed [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it 2 skipped 38 passed (1.1m)

112 skipped 553 passed (5.4m)

13 passed (50.2s)

13 passed (10.2s)

5 passed (45.5s)

5 passed (11.6s)

4 skipped 10 passed (37.2s)

2 skipped 12 passed (8.0s)

13 passed (52.4s)

13 passed (9.5s)

1 failed [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it 2 skipped 38 passed (1.1m)

1 failed [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it 2 skipped 38 passed (1.0m)

4 skipped 10 passed (26.1s)

2 skipped 12 passed (7.7s)

474 skipped 191 passed (38.0s)

2 skipped 29 passed (1.2m)

2 skipped 29 passed (38.7s)

1 failed [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it 2 skipped 38 passed (1.1m)

1 failed [chromium] › tests/middleware.test.ts:62:5 › Should trace outgoing fetch requests inside middleware and create breadcrumbs for it 2 skipped 38 passed (1.0m)