Size limit has been exceeded.

Process completed with exit code 1.

AssertionError: expected 'sentry-environment=production,sentry-…' to be undefined - Expected: undefined + Received: "sentry-environment=production,sentry-release=1.0,sentry-public_key=public,sentry-trace_id=fdb87240ecba43ac89f888e9ea83a608" ❯ suites/tracing/requests/http-no-tracing-no-spans/test.ts:118:40 ❯ ../test-utils/src/server.ts:60:13 ❯ Layer.handle [as handle_request] ../../node_modules/express/lib/router/layer.js:95:5 ❯ next ../../node_modules/express/lib/router/route.js:149:13 ❯ Route.dispatch ../../node_modules/express/lib/router/route.js:119:3 ❯ Layer.handle [as handle_request] ../../node_modules/express/lib/router/layer.js:95:5 ❯ ../../node_modules/express/lib/router/index.js:284:15 ❯ Function.process_params ../../node_modules/express/lib/router/index.js:346:12 ❯ next ../../node_modules/express/lib/router/index.js:280:10 ❯ expressInit ../../node_modules/express/lib/middleware/init.js:40:5

AssertionError: expected 'sentry-environment=production,sentry-…' to be undefined - Expected: undefined + Received: "sentry-environment=production,sentry-release=1.0,sentry-public_key=public,sentry-trace_id=8852c540f7474815ab0e91a2f6ce3ae3" ❯ suites/tracing/requests/http-no-tracing-no-spans/test.ts:118:40 ❯ ../test-utils/src/server.ts:60:13 ❯ Layer.handle [as handle_request] ../../node_modules/express/lib/router/layer.js:95:5 ❯ next ../../node_modules/express/lib/router/route.js:149:13 ❯ Route.dispatch ../../node_modules/express/lib/router/route.js:119:3 ❯ Layer.handle [as handle_request] ../../node_modules/express/lib/router/layer.js:95:5 ❯ ../../node_modules/express/lib/router/index.js:284:15 ❯ Function.process_params ../../node_modules/express/lib/router/index.js:346:12 ❯ next ../../node_modules/express/lib/router/index.js:280:10 ❯ expressInit ../../node_modules/express/lib/middleware/init.js:40:5

Process completed with exit code 1.

AssertionError: expected 'sentry-environment=production,sentry-…' to be undefined - Expected: undefined + Received: "sentry-environment=production,sentry-release=1.0,sentry-public_key=public,sentry-trace_id=3d0d708409074be9a071d764422319d7" ❯ suites/tracing/requests/http-no-tracing-no-spans/test.ts:118:40 ❯ ../test-utils/src/server.ts:60:13 ❯ Layer.handle [as handle_request] ../../node_modules/express/lib/router/layer.js:95:5 ❯ next ../../node_modules/express/lib/router/route.js:149:13 ❯ Route.dispatch ../../node_modules/express/lib/router/route.js:119:3 ❯ Layer.handle [as handle_request] ../../node_modules/express/lib/router/layer.js:95:5 ❯ ../../node_modules/express/lib/router/index.js:284:15 ❯ Function.process_params ../../node_modules/express/lib/router/index.js:346:12 ❯ next ../../node_modules/express/lib/router/index.js:280:10 ❯ expressInit ../../node_modules/express/lib/middleware/init.js:40:5

AssertionError: expected 'sentry-environment=production,sentry-…' to be undefined - Expected: undefined + Received: "sentry-environment=production,sentry-release=1.0,sentry-public_key=public,sentry-trace_id=4f5ecc5c5bca41e089bc10b5bf3ef0fc" ❯ suites/tracing/requests/http-no-tracing-no-spans/test.ts:118:40 ❯ ../test-utils/src/server.ts:60:13 ❯ Layer.handle [as handle_request] ../../node_modules/express/lib/router/layer.js:95:5 ❯ next ../../node_modules/express/lib/router/route.js:149:13 ❯ Route.dispatch ../../node_modules/express/lib/router/route.js:119:3 ❯ Layer.handle [as handle_request] ../../node_modules/express/lib/router/layer.js:95:5 ❯ ../../node_modules/express/lib/router/index.js:284:15 ❯ Function.process_params ../../node_modules/express/lib/router/index.js:346:12 ❯ next ../../node_modules/express/lib/router/index.js:280:10 ❯ expressInit ../../node_modules/express/lib/middleware/init.js:40:5

Process completed with exit code 1.

An index signature parameter type must be either 'string' or 'number'.

Process completed with exit code 1.

1) [chromium] › tests/server.test.ts:120:5 › Should record spans from http instrumentation ─────── Error: expect(received).toEqual(expected) // deep equality - Expected - 5 + Received + 15 @@ -1,27 +1,37 @@ Object { - "data": ObjectContaining { + "data": Object { "http.flavor": "1.1", - "http.host": "example.com:80", + "http.host": "example.com", "http.method": "GET", + "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", - "net.peer.ip": Any<String>, + "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", + "network.peer.address": "172.66.147.243", + "network.peer.port": 80, + "network.protocol.version": "1.1", + "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", - "sentry.origin": "auto.http.otel.http", + "sentry.origin": "auto.http.client", + "sentry.source": "route", "url": "http://example.com/", + "url.domain": "example.com", + "url.full": "http://example.com/", + "url.path": "/", + "url.scheme": "http:", }, "description": "GET http://example.com/", "op": "http.client", - "origin": "auto.http.otel.http", + "origin": "auto.http.client", "parent_span_id": StringMatching /[a-f0-9]{16}/, "span_id": StringMatching /[a-f0-9]{16}/, "start_timestamp": Any<Number>, "status": "ok", "timestamp": Any<Number>, 129 | const httpClientSpan = transactionEvent.spans?.find(span => span.op === 'http.client'); 130 | > 131 | expect(httpClientSpan).toEqual({ | ^ 132 | span_id: expect.stringMatching(/[a-f0-9]{16}/), 133 | trace_id: expect.stringMatching(/[a-f0-9]{32}/), 134 | data: expect.objectContaining({ at /home/runner/work/_temp/test-application/tests/server.test.ts:131:26

Process completed with exit code 1.

2) [chromium] › tests/spans.test.ts:179:5 › OTel span appears as child of Sentry span (interop) ── Error: expect(received).toEqual(expected) // deep equality - Expected - 0 + Received + 4 @@ -46,10 +46,14 @@ }, "http.response.status_code": Object { "type": "integer", "value": Any<Number>, }, + "http.url": Object { + "type": "string", + "value": "http://localhost:3030/test-interop", + }, "sentry.environment": Object { "type": "string", "value": "qa", }, "sentry.op": Object { 189 | 190 | const httpServerSpan = spans.find(span => getSpanOp(span) === 'http.server'); > 191 | expect(httpServerSpan).toEqual({ | ^ 192 | ...SEGMENT_SPAN, 193 | name: 'GET /test-interop', 194 | attributes: { at /home/runner/work/_temp/test-application/tests/spans.test.ts:191:26

1) [chromium] › tests/spans.test.ts:128:5 › Sends streamed spans (http.server and manual with Sentry.startSpan) Error: expect(received).toEqual(expected) // deep equality - Expected - 0 + Received + 4 @@ -83,10 +83,14 @@ }, "http.response.status_code": Object { "type": "integer", "value": Any<Number>, }, + "http.url": Object { + "type": "string", + "value": "http://localhost:3030/test-sentry-span", + }, "sentry.environment": Object { "type": "string", "value": "qa", }, "sentry.op": Object { 136 | expect(spans).toHaveLength(2); 137 | > 138 | expect(spans).toEqual([ | ^ 139 | { 140 | attributes: { 141 | 'sentry.environment': { at /home/runner/work/_temp/test-application/tests/spans.test.ts:138:17

Process completed with exit code 1.

1) [chromium] › tests/request-instrumentation.test.ts:4:5 › Should send a transaction with a fetch span Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"http.method": "GET", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.http"}, "description": "GET https://github.com/"} Received array: [{"data": {"next.route": "/request-instrumentation", "next.span_name": "resolve page components", "next.span_type": "NextNodeServer.findPageComponents", "sentry.origin": "auto"}, "description": "resolve page components", "origin": "auto", "parent_span_id": "37b5149234332b5a", "span_id": "6014e730d85dae39", "start_timestamp": 1776694604.846, "status": "ok", "timestamp": 1776694604.849376, "trace_id": "4ed1aa9a9b0139c38604eaa79c6be702"}, {"data": {"next.route": "/request-instrumentation", "next.span_name": "render route (app) /request-instrumentation", "next.span_type": "AppRender.getBodyResult", "sentry.origin": "auto"}, "description": "render route (app) /request-instrumentation", "origin": "auto", "parent_span_id": "37b5149234332b5a", "span_id": "b3832f86bff63ae0", "start_timestamp": 1776694604.85, "status": "ok", "timestamp": 1776694605.0080678, "trace_id": "4ed1aa9a9b0139c38604eaa79c6be702"}, {"data": {"next.span_name": "build component tree", "next.span_type": "NextNodeServer.createComponentTree", "sentry.origin": "auto"}, "description": "build component tree", "origin": "auto", "parent_span_id": "b3832f86bff63ae0", "span_id": "dcd6d8721ab2b76b", "start_timestamp": 1776694604.85, "status": "ok", "timestamp": 1776694604.8509, "trace_id": "4ed1aa9a9b0139c38604eaa79c6be702"}, {"data": {"next.segment": "", "next.span_name": "resolve segment modules", "next.span_type": "NextNodeServer.getLayoutOrPageModule", "sentry.nextjs.ssr.function.route": "/request-instrumentation", "sentry.nextjs.ssr.function.type": "Layout", "sentry.op": "function.nextjs", "sentry.origin": "auto"}, "description": "resolve root layout server component", "op": "function.nextjs", "origin": "auto", "parent_span_id": "dcd6d8721ab2b76b", "span_id": "f89ab9d15d226d0f", "start_timestamp": 1776694604.851, "status": "ok", "timestamp": 1776694604.851185, "trace_id": "4ed1aa9a9b0139c38604eaa79c6be702"}, {"data": {"next.segment": "__PAGE__", "next.span_name": "resolve segment modules", "next.span_type": "NextNodeServer.getLayoutOrPageModule", "sentry.nextjs.ssr.function.route": "/request-instrumentation", "sentry.nextjs.ssr.function.type": "Page", "sentry.op": "function.nextjs", "sentry.origin": "auto"}, "description": "resolve page server component \"/request-instrumentation\"", "op": "function.nextjs", "origin": "auto", "parent_span_id": "dcd6d8721ab2b76b", "span_id": "c784119454458b0c", "start_timestamp": 1776694604.851, "status": "ok", "timestamp": 1776694604.8511205, "trace_id": "4ed1aa9a9b0139c38604eaa79c6be702"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "140.82.114.4", "network.peer.port": 443, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "github.com", "server.port": 443, "url": "https://github.com/", "url.full": "https://github.com/", "url.path": "/", "url.query": "", "url.scheme": "https", "user_agent.original": "node"}, "description": "GET https://github.com/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "b3832f86bff63ae0", "span_id": "af8728010b6736bf", "start_timestamp": 1776694604.854, "status": "ok", "timestamp": 1776694604.9318821, "trace_id": "4ed1aa9a9b0139c38604eaa79c6be702"}, {"data": {"http.flavor": "1.1", "http.host": "github.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "https://github.com/", "net.peer.ip": "140.82.114.4", "net.peer.name": "github.com", "net.peer.port": 443, "net.transport": "ip_tcp", "network.peer.address":

Process completed with exit code 1.

1) [chromium] › tests/request-instrumentation.test.ts:4:5 › Should send a transaction with a fetch span Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"http.method": "GET", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.http"}, "description": "GET https://github.com/"} Received array: [{"data": {"next.route": "/request-instrumentation", "next.span_name": "resolve page components", "next.span_type": "NextNodeServer.findPageComponents", "sentry.origin": "auto"}, "description": "resolve page components", "origin": "auto", "parent_span_id": "8e286af5a00910ff", "span_id": "1d22df2cff7c7c76", "start_timestamp": 1776694605.24, "status": "ok", "timestamp": 1776694605.2425473, "trace_id": "10e4b07d624923a5de4bad590e144b64"}, {"data": {"next.route": "/request-instrumentation", "next.span_name": "render route (app) /request-instrumentation", "next.span_type": "AppRender.getBodyResult", "sentry.origin": "auto"}, "description": "render route (app) /request-instrumentation", "origin": "auto", "parent_span_id": "8e286af5a00910ff", "span_id": "214015ecce3dea02", "start_timestamp": 1776694605.243, "status": "ok", "timestamp": 1776694605.4009829, "trace_id": "10e4b07d624923a5de4bad590e144b64"}, {"data": {"next.span_name": "build component tree", "next.span_type": "NextNodeServer.createComponentTree", "sentry.origin": "auto"}, "description": "build component tree", "origin": "auto", "parent_span_id": "214015ecce3dea02", "span_id": "ca9f425a8c2b7389", "start_timestamp": 1776694605.246, "status": "ok", "timestamp": 1776694605.2469819, "trace_id": "10e4b07d624923a5de4bad590e144b64"}, {"data": {"next.segment": "", "next.span_name": "resolve segment modules", "next.span_type": "NextNodeServer.getLayoutOrPageModule", "sentry.nextjs.ssr.function.route": "/request-instrumentation", "sentry.nextjs.ssr.function.type": "Layout", "sentry.op": "function.nextjs", "sentry.origin": "auto"}, "description": "resolve root layout server component", "op": "function.nextjs", "origin": "auto", "parent_span_id": "ca9f425a8c2b7389", "span_id": "b8fbc8c33d969edb", "start_timestamp": 1776694605.247, "status": "ok", "timestamp": 1776694605.2471626, "trace_id": "10e4b07d624923a5de4bad590e144b64"}, {"data": {"next.segment": "__PAGE__", "next.span_name": "resolve segment modules", "next.span_type": "NextNodeServer.getLayoutOrPageModule", "sentry.nextjs.ssr.function.route": "/request-instrumentation", "sentry.nextjs.ssr.function.type": "Page", "sentry.op": "function.nextjs", "sentry.origin": "auto"}, "description": "resolve page server component \"/request-instrumentation\"", "op": "function.nextjs", "origin": "auto", "parent_span_id": "ca9f425a8c2b7389", "span_id": "5b15d15be9a2fe14", "start_timestamp": 1776694605.247, "status": "ok", "timestamp": 1776694605.2471166, "trace_id": "10e4b07d624923a5de4bad590e144b64"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "140.82.113.4", "network.peer.port": 443, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "github.com", "server.port": 443, "url": "https://github.com/", "url.full": "https://github.com/", "url.path": "/", "url.query": "", "url.scheme": "https", "user_agent.original": "node"}, "description": "GET https://github.com/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "214015ecce3dea02", "span_id": "d8a66a7e2687cbe0", "start_timestamp": 1776694605.25, "status": "ok", "timestamp": 1776694605.326053, "trace_id": "10e4b07d624923a5de4bad590e144b64"}, {"data": {"http.flavor": "1.1", "http.host": "github.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "https://github.com/", "net.peer.ip": "140.82.113.4", "net.peer.name": "github.com", "net.peer.port": 443, "net.transport": "ip_tcp", "network.peer.addres

Process completed with exit code 1.

1) [chromium] › tests/request-instrumentation.test.ts:4:5 › Should send a transaction with a fetch span Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"http.method": "GET", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.http"}, "description": "GET https://github.com/"} Received array: [{"data": {"next.route": "/request-instrumentation", "next.span_name": "resolve page components", "next.span_type": "NextNodeServer.findPageComponents", "sentry.origin": "auto"}, "description": "resolve page components", "origin": "auto", "parent_span_id": "0f7454c242602c68", "span_id": "868c53913d3053dd", "start_timestamp": 1776694638.235, "status": "ok", "timestamp": 1776694638.23525, "trace_id": "693dfc48f5ea1dbdcc1b7ea144736cfb"}, {"data": {"next.route": "/request-instrumentation", "next.span_name": "render route (app) /request-instrumentation", "next.span_type": "AppRender.getBodyResult", "sentry.origin": "auto"}, "description": "render route (app) /request-instrumentation", "origin": "auto", "parent_span_id": "0f7454c242602c68", "span_id": "028d5df47bdb4e6f", "start_timestamp": 1776694638.24, "status": "ok", "timestamp": 1776694638.5724442, "trace_id": "693dfc48f5ea1dbdcc1b7ea144736cfb"}, {"data": {"next.span_name": "build component tree", "next.span_type": "NextNodeServer.createComponentTree", "sentry.origin": "auto"}, "description": "build component tree", "origin": "auto", "parent_span_id": "028d5df47bdb4e6f", "span_id": "8e1be9e49895db70", "start_timestamp": 1776694638.242, "status": "ok", "timestamp": 1776694638.2428117, "trace_id": "693dfc48f5ea1dbdcc1b7ea144736cfb"}, {"data": {"next.segment": "", "next.span_name": "resolve segment modules", "next.span_type": "NextNodeServer.getLayoutOrPageModule", "sentry.nextjs.ssr.function.route": "/request-instrumentation", "sentry.nextjs.ssr.function.type": "Layout", "sentry.op": "function.nextjs", "sentry.origin": "auto"}, "description": "resolve root layout server component", "op": "function.nextjs", "origin": "auto", "parent_span_id": "8e1be9e49895db70", "span_id": "7aec4dddcae8a1d8", "start_timestamp": 1776694638.242, "status": "ok", "timestamp": 1776694638.242143, "trace_id": "693dfc48f5ea1dbdcc1b7ea144736cfb"}, {"data": {"next.segment": "__PAGE__", "next.span_name": "resolve segment modules", "next.span_type": "NextNodeServer.getLayoutOrPageModule", "sentry.nextjs.ssr.function.route": "/request-instrumentation", "sentry.nextjs.ssr.function.type": "Page", "sentry.op": "function.nextjs", "sentry.origin": "auto"}, "description": "resolve page server component \"/request-instrumentation\"", "op": "function.nextjs", "origin": "auto", "parent_span_id": "8e1be9e49895db70", "span_id": "7a9441fcaa44bf90", "start_timestamp": 1776694638.243, "status": "ok", "timestamp": 1776694638.2430913, "trace_id": "693dfc48f5ea1dbdcc1b7ea144736cfb"}, {"data": {"http.request.method": "GET", "http.request.method_original": "GET", "http.response.status_code": 200, "network.peer.address": "140.82.116.4", "network.peer.port": 443, "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.otel.node_fetch", "server.address": "github.com", "server.port": 443, "url": "https://github.com/", "url.full": "https://github.com/", "url.path": "/", "url.query": "", "url.scheme": "https", "user_agent.original": "node"}, "description": "GET https://github.com/", "op": "http.client", "origin": "auto.http.otel.node_fetch", "parent_span_id": "028d5df47bdb4e6f", "span_id": "7b3c08d1e0b6ba44", "start_timestamp": 1776694638.245, "status": "ok", "timestamp": 1776694638.3873968, "trace_id": "693dfc48f5ea1dbdcc1b7ea144736cfb"}, {"data": {"http.flavor": "1.1", "http.host": "github.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "https://github.com/", "net.peer.ip": "140.82.116.4", "net.peer.name": "github.com", "net.peer.port": 443, "net.transport": "ip_tcp", "network.peer.address

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, "http.url": "http://localhost:3030/", "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": "eca3bac023179f2b", "span_id": "289f4591abbcf1d4", "start_timestamp": 1776694603.428, "status": "ok", "timestamp": 1776694603.452357, "trace_id": "8e4a6c83d60d94f6f4b6a159db9e47f2"}, {"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": "289f4591abbcf1d4", "span_id": "2d4ecfb5546ac44a", "start_timestamp": 1776694603.434, "status": "ok", "timestamp": 1776694603.449999, "trace_id": "8e4a6c83d60d94f6f4b6a159db9e47f2"}] 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 /home/runner/work/_temp/test-application/tests/middleware.test.ts:100:41

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

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

Process completed with exit code 1.

4) [chromium] › tests/npm.test.ts:74:7 › NPM package › tracing in ESM works ────────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "172.66.147.243", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "fff6f4752433e060", "span_id": "0d5daada1c37ffa4", "start_timestamp": 1776694655.234, "status": "ok", "timestamp": 1776694655.2512603, "trace_id": "c3901430c9cb865cbfb6576b2b2228ba"}, {"data": {"sentry.op": "manual", "sentry.origin": "manual"}, "description": "manual-span", "op": "manual", "origin": "manual", "parent_span_id": "fff6f4752433e060", "span_id": "8c6573995e41532d", "start_timestamp": 1776694655.253, "status": "ok", "timestamp": 1776694655.2534416, "trace_id": "c3901430c9cb865cbfb6576b2b2228ba"}] 110 | 111 | // shows that the Otel Http instrumentation is working > 112 | expect(transactionEvent.spans).toContainEqual( | ^ 113 | expect.objectContaining({ 114 | data: expect.objectContaining({ 115 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/npm.test.ts:112:36

3) [chromium] › tests/npm.test.ts:6:7 › NPM package › tracing in CJS works ─────────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "172.66.147.243", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "c827c3d19234b4a0", "span_id": "7cba2c8276f8f172", "start_timestamp": 1776694633.87, "status": "ok", "timestamp": 1776694633.891215, "trace_id": "7e36dc48b5899cb3997110a5672e9c97"}, {"data": {"sentry.op": "manual", "sentry.origin": "manual"}, "description": "manual-span", "op": "manual", "origin": "manual", "parent_span_id": "c827c3d19234b4a0", "span_id": "50dae6734e87c1d8", "start_timestamp": 1776694633.893, "status": "ok", "timestamp": 1776694633.8934383, "trace_id": "7e36dc48b5899cb3997110a5672e9c97"}] 42 | 43 | // shows that the Otel Http instrumentation is working > 44 | expect(transactionEvent.spans).toContainEqual( | ^ 45 | expect.objectContaining({ 46 | data: expect.objectContaining({ 47 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/npm.test.ts:44:36

2) [chromium] › tests/layer.test.ts:74:7 › Lambda layer › tracing in ESM works ─────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"sentry.op": "test", "sentry.origin": "manual"}, "description": "manual-span", "op": "test", "origin": "manual", "parent_span_id": "1e55d77d04d3ab6d", "span_id": "8c523a2283983e33", "start_timestamp": 1776694609.583, "status": "ok", "timestamp": 1776694609.6245022, "trace_id": "c1ad89b6312e39e8a092caa0bc7b365b"}, {"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "172.66.147.243", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "8c523a2283983e33", "span_id": "9d86c3971ebc52ad", "start_timestamp": 1776694609.592, "status": "ok", "timestamp": 1776694609.6229875, "trace_id": "c1ad89b6312e39e8a092caa0bc7b365b"}] 110 | 111 | // shows that the Otel Http instrumentation is working > 112 | expect(transactionEvent.spans).toContainEqual( | ^ 113 | expect.objectContaining({ 114 | data: expect.objectContaining({ 115 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/layer.test.ts:112:36

1) [chromium] › tests/layer.test.ts:6:7 › Lambda layer › tracing in CJS works ──────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"sentry.op": "test", "sentry.origin": "manual"}, "description": "manual-span", "op": "test", "origin": "manual", "parent_span_id": "64626754ebb2e574", "span_id": "4787c25d02ad94ac", "start_timestamp": 1776694588.701, "status": "ok", "timestamp": 1776694588.7321131, "trace_id": "b8ffb86ebb8bc3d125fd024dabacca6b"}, {"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "172.66.147.243", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "4787c25d02ad94ac", "span_id": "0a9200cb31dc16ad", "start_timestamp": 1776694588.71, "status": "ok", "timestamp": 1776694588.7309246, "trace_id": "b8ffb86ebb8bc3d125fd024dabacca6b"}] 42 | 43 | // shows that the Otel Http instrumentation is working > 44 | expect(transactionEvent.spans).toContainEqual( | ^ 45 | expect.objectContaining({ 46 | data: expect.objectContaining({ 47 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/layer.test.ts:44:36

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, "http.url": "http://localhost:3030/", "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": "c9ffc269e55f60f6", "span_id": "5547bdafe2ae5f5f", "start_timestamp": 1776694612.792, "status": "ok", "timestamp": 1776694612.8166711, "trace_id": "242a5611c28bf40793ce72eacd30fb38"}, {"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": "5547bdafe2ae5f5f", "span_id": "7c091869d9893a1f", "start_timestamp": 1776694612.798, "status": "ok", "timestamp": 1776694612.8144102, "trace_id": "242a5611c28bf40793ce72eacd30fb38"}] 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 /home/runner/work/_temp/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, "http.url": "http://localhost:3030/", "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": "79ae5b2523d4caf1", "span_id": "44d756a75c90d1f1", "start_timestamp": 1776694610.424, "status": "ok", "timestamp": 1776694610.4465287, "trace_id": "36d86ed91849f81a8ae859482e952578"}, {"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": "44d756a75c90d1f1", "span_id": "c66327c8397757cd", "start_timestamp": 1776694610.43, "status": "ok", "timestamp": 1776694610.4448931, "trace_id": "36d86ed91849f81a8ae859482e952578"}] 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 /home/runner/work/_temp/test-application/tests/middleware.test.ts:100:41

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.

4) [chromium] › tests/npm.test.ts:74:7 › NPM package › tracing in ESM works ────────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "172.66.147.243", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "29513a2c2baa7d8e", "span_id": "7c03e020c56a5a9b", "start_timestamp": 1776694668.039, "status": "ok", "timestamp": 1776694668.0610213, "trace_id": "e81b1dd5b3be22e04bbcdc20faecc005"}, {"data": {"sentry.op": "manual", "sentry.origin": "manual"}, "description": "manual-span", "op": "manual", "origin": "manual", "parent_span_id": "29513a2c2baa7d8e", "span_id": "5daaa35261943972", "start_timestamp": 1776694668.063, "status": "ok", "timestamp": 1776694668.0635035, "trace_id": "e81b1dd5b3be22e04bbcdc20faecc005"}] 110 | 111 | // shows that the Otel Http instrumentation is working > 112 | expect(transactionEvent.spans).toContainEqual( | ^ 113 | expect.objectContaining({ 114 | data: expect.objectContaining({ 115 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/npm.test.ts:112:36

3) [chromium] › tests/npm.test.ts:6:7 › NPM package › tracing in CJS works ─────────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "172.66.147.243", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "7fda501b253e66bd", "span_id": "e10803ea5b33110f", "start_timestamp": 1776694645.413, "status": "ok", "timestamp": 1776694645.434235, "trace_id": "5baa4a02acb517a40c7b91f6a2975a04"}, {"data": {"sentry.op": "manual", "sentry.origin": "manual"}, "description": "manual-span", "op": "manual", "origin": "manual", "parent_span_id": "7fda501b253e66bd", "span_id": "3658f7b595f5b561", "start_timestamp": 1776694645.436, "status": "ok", "timestamp": 1776694645.4364824, "trace_id": "5baa4a02acb517a40c7b91f6a2975a04"}] 42 | 43 | // shows that the Otel Http instrumentation is working > 44 | expect(transactionEvent.spans).toContainEqual( | ^ 45 | expect.objectContaining({ 46 | data: expect.objectContaining({ 47 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/npm.test.ts:44:36

2) [chromium] › tests/layer.test.ts:74:7 › Lambda layer › tracing in ESM works ─────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"sentry.op": "test", "sentry.origin": "manual"}, "description": "manual-span", "op": "test", "origin": "manual", "parent_span_id": "ecdaabf342a4da13", "span_id": "79c830dd821c13e7", "start_timestamp": 1776694619.254, "status": "ok", "timestamp": 1776694619.2853634, "trace_id": "e4d7ec95ad059e165787843c227561b1"}, {"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "104.20.23.154", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "104.20.23.154", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "79c830dd821c13e7", "span_id": "6e84a2cc55499362", "start_timestamp": 1776694619.264, "status": "ok", "timestamp": 1776694619.284298, "trace_id": "e4d7ec95ad059e165787843c227561b1"}] 110 | 111 | // shows that the Otel Http instrumentation is working > 112 | expect(transactionEvent.spans).toContainEqual( | ^ 113 | expect.objectContaining({ 114 | data: expect.objectContaining({ 115 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/layer.test.ts:112:36

1) [chromium] › tests/layer.test.ts:6:7 › Lambda layer › tracing in CJS works ──────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"sentry.op": "test", "sentry.origin": "manual"}, "description": "manual-span", "op": "test", "origin": "manual", "parent_span_id": "ab1cc8e2fabab497", "span_id": "eef9695948d57ab9", "start_timestamp": 1776694595.354, "status": "ok", "timestamp": 1776694595.3880293, "trace_id": "3a5550d72c4c15d9ba655b58d2390488"}, {"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "172.66.147.243", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "eef9695948d57ab9", "span_id": "204e3f20477adf3f", "start_timestamp": 1776694595.363, "status": "ok", "timestamp": 1776694595.3865893, "trace_id": "3a5550d72c4c15d9ba655b58d2390488"}] 42 | 43 | // shows that the Otel Http instrumentation is working > 44 | expect(transactionEvent.spans).toContainEqual( | ^ 45 | expect.objectContaining({ 46 | data: expect.objectContaining({ 47 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/layer.test.ts:44:36

Process completed with exit code 1.

4) [chromium] › tests/npm.test.ts:74:7 › NPM package › tracing in ESM works ────────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "172.66.147.243", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "172.66.147.243", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "c00d7b69ee61e738", "span_id": "76b7cc4b39429194", "start_timestamp": 1776694670.196, "status": "ok", "timestamp": 1776694670.2497926, "trace_id": "37dff51d88ed40a2d68c30d3328aa0d9"}, {"data": {"sentry.op": "manual", "sentry.origin": "manual"}, "description": "manual-span", "op": "manual", "origin": "manual", "parent_span_id": "c00d7b69ee61e738", "span_id": "07dd23c30c4206e5", "start_timestamp": 1776694670.251, "status": "ok", "timestamp": 1776694670.2514286, "trace_id": "37dff51d88ed40a2d68c30d3328aa0d9"}] 110 | 111 | // shows that the Otel Http instrumentation is working > 112 | expect(transactionEvent.spans).toContainEqual( | ^ 113 | expect.objectContaining({ 114 | data: expect.objectContaining({ 115 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/npm.test.ts:112:36

3) [chromium] › tests/npm.test.ts:6:7 › NPM package › tracing in CJS works ─────────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "104.20.23.154", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "104.20.23.154", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "7ff5a73c7b0b905a", "span_id": "e91881fe3635a5ef", "start_timestamp": 1776694650.422, "status": "ok", "timestamp": 1776694650.4632242, "trace_id": "84e8fce87d2a9305313d9f91f89d7169"}, {"data": {"sentry.op": "manual", "sentry.origin": "manual"}, "description": "manual-span", "op": "manual", "origin": "manual", "parent_span_id": "7ff5a73c7b0b905a", "span_id": "ff1194ab171594fe", "start_timestamp": 1776694650.465, "status": "ok", "timestamp": 1776694650.4654095, "trace_id": "84e8fce87d2a9305313d9f91f89d7169"}] 42 | 43 | // shows that the Otel Http instrumentation is working > 44 | expect(transactionEvent.spans).toContainEqual( | ^ 45 | expect.objectContaining({ 46 | data: expect.objectContaining({ 47 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/npm.test.ts:44:36

2) [chromium] › tests/layer.test.ts:74:7 › Lambda layer › tracing in ESM works ─────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"sentry.op": "test", "sentry.origin": "manual"}, "description": "manual-span", "op": "test", "origin": "manual", "parent_span_id": "2526a97a74265baa", "span_id": "75674bd150cb13bc", "start_timestamp": 1776694626.991, "status": "ok", "timestamp": 1776694627.03766, "trace_id": "03c77227f9229d1de409f63db09b535b"}, {"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "104.20.23.154", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "104.20.23.154", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "75674bd150cb13bc", "span_id": "a74d8499d001a87e", "start_timestamp": 1776694626.997, "status": "ok", "timestamp": 1776694627.0368536, "trace_id": "03c77227f9229d1de409f63db09b535b"}] 110 | 111 | // shows that the Otel Http instrumentation is working > 112 | expect(transactionEvent.spans).toContainEqual( | ^ 113 | expect.objectContaining({ 114 | data: expect.objectContaining({ 115 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/layer.test.ts:112:36

1) [chromium] › tests/layer.test.ts:6:7 › Lambda layer › tracing in CJS works ──────────────────── Error: expect(received).toContainEqual(expected) // deep equality Expected value: ObjectContaining {"data": ObjectContaining {"sentry.op": "http.client", "sentry.origin": "auto.http.otel.http", "url": "http://example.com/"}, "description": "GET http://example.com/", "op": "http.client"} Received array: [{"data": {"sentry.op": "test", "sentry.origin": "manual"}, "description": "manual-span", "op": "test", "origin": "manual", "parent_span_id": "37b4e3158ab3ea6f", "span_id": "f1a6ebb7969724fa", "start_timestamp": 1776694607.176, "status": "ok", "timestamp": 1776694607.230504, "trace_id": "058eb899fac5beebf4903617d02c17bc"}, {"data": {"http.flavor": "1.1", "http.host": "example.com", "http.method": "GET", "http.request.method": "GET", "http.response.status_code": 200, "http.status_code": 200, "http.status_text": "OK", "http.target": "/", "http.url": "http://example.com/", "net.peer.ip": "104.20.23.154", "net.peer.name": "example.com", "net.peer.port": 80, "net.transport": "ip_tcp", "network.peer.address": "104.20.23.154", "network.peer.port": 80, "network.protocol.version": "1.1", "network.transport": "ip_tcp", "otel.kind": "CLIENT", "sentry.op": "http.client", "sentry.origin": "auto.http.client", "sentry.source": "route", "url": "http://example.com/", "url.domain": "example.com", "url.full": "http://example.com/", "url.path": "/", "url.scheme": "http:"}, "description": "GET http://example.com/", "op": "http.client", "origin": "auto.http.client", "parent_span_id": "f1a6ebb7969724fa", "span_id": "d800ed4de846a4be", "start_timestamp": 1776694607.182, "status": "ok", "timestamp": 1776694607.228736, "trace_id": "058eb899fac5beebf4903617d02c17bc"}] 42 | 43 | // shows that the Otel Http instrumentation is working > 44 | expect(transactionEvent.spans).toContainEqual( | ^ 45 | expect.objectContaining({ 46 | data: expect.objectContaining({ 47 | 'sentry.op': 'http.client', at /home/runner/work/_temp/test-application/tests/layer.test.ts:44:36

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, "http.url": "http://localhost:3030/", "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": "f6c0dc20b8350d45", "span_id": "60659ab6c6c13954", "start_timestamp": 1776694632.152, "status": "ok", "timestamp": 1776694632.1801968, "trace_id": "b2c1c5f8796b70e741d9451485ba877a"}, {"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": "60659ab6c6c13954", "span_id": "64e5d82a36b28153", "start_timestamp": 1776694632.152, "status": "ok", "timestamp": 1776694632.1791987, "trace_id": "b2c1c5f8796b70e741d9451485ba877a"}, {"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": "64e5d82a36b28153", "span_id": "d89cccdeac10a3eb", "start_timestamp": 1776694632.158, "status": "ok", "timestamp": 1776694632.1767762, "trace_id": "b2c1c5f8796b70e741d9451485ba877a"}] 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 /home/runner/work/_temp/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, "http.url": "http://localhost:3030/", "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": "e02ff9aacdb350ee", "span_id": "191ea0e3b39ff14e", "start_timestamp": 1776694636.921, "status": "ok", "timestamp": 1776694636.9495602, "trace_id": "7ff0bca4050d6b6eab13b7a3be0b8420"}, {"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": "191ea0e3b39ff14e", "span_id": "c96b0cdf0479cdc3", "start_timestamp": 1776694636.922, "status": "ok", "timestamp": 1776694636.9496171, "trace_id": "7ff0bca4050d6b6eab13b7a3be0b8420"}, {"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": "c96b0cdf0479cdc3", "span_id": "7aa4d3b1c7b15c36", "start_timestamp": 1776694636.927, "status": "ok", "timestamp": 1776694636.9461803, "trace_id": "7ff0bca4050d6b6eab13b7a3be0b8420"}] 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 /home/runner/work/_temp/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, "http.url": "http://localhost:3030/", "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": "10adcd5f54804846", "span_id": "84e93a0a0bdbffd7", "start_timestamp": 1776694636.61, "status": "ok", "timestamp": 1776694636.6384332, "trace_id": "6c550e5077360a9fb5c5a95dbc5122fd"}, {"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": "84e93a0a0bdbffd7", "span_id": "93860c33c03c15f7", "start_timestamp": 1776694636.61, "status": "ok", "timestamp": 1776694636.6368008, "trace_id": "6c550e5077360a9fb5c5a95dbc5122fd"}, {"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": "93860c33c03c15f7", "span_id": "a0c148c9c9bf34da", "start_timestamp": 1776694636.616, "status": "ok", "timestamp": 1776694636.6336558, "trace_id": "6c550e5077360a9fb5c5a95dbc5122fd"}] 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 /home/runner/work/_temp/test-application/tests/middleware.test.ts:100:41

Process completed with exit code 1.

Error: Test timed out in 15000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ suites/cron/cron/test.ts:8:1

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/

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.

Type 'ClientRequest' 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: denoland/setup-deno@v2.0.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./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 check failed: 20.51% < target 80%

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

❌ Project coverage check failed: 64.10% (-0.06%) relative to base

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

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

❌ Project coverage check failed: 65.02% (-0.05%) relative to base

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: /home/runner/work/_temp/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/

Patch coverage defaulted to 100% because no changed files matched coverage data. Unmatched diff files: dev-packages/cloudflare-integration-tests/suites/public-api/startSpan-streamed/test.ts, dev-packages/e2e-tests/test-applications/nextjs-16/tests/middleware.test.ts, dev-packages/node-integration-tests/suites/tracing/http-client-spans/http-basic/test.ts, dev-packages/node-integration-tests/suites/tracing/http-client-spans/http-strip-query/test.ts, dev-packages/node-integration-tests/suites/tracing/requests/http-no-tracing-no-spans/test.ts, packages/cloudflare/test/request.test.ts, packages/core/src/index.ts, packages/core/src/integrations/express/index.ts, packages/core/src/integrations/express/utils.ts, packages/core/src/integrations/http/add-outgoing-request-breadcrumb.ts, packages/core/src/integrations/http/client-patch.ts, packages/core/src/integrations/http/client-subscriptions.ts, packages/core/src/integrations/http/constants.ts, packages/core/src/integrations/http/get-outgoing-span-data.ts, packages/core/src/integrations/http/get-request-url.ts, packages/core/src/integrations/http/index.ts, packages/core/src/integrations/http/inject-trace-propagation-headers.ts, packages/core/src/integrations/http/instrument-outgoing-request.ts, packages/core/src/integrations/http/merge-baggage.ts, packages/core/src/integrations/http/types.ts, packages/core/src/tracing/index.ts, packages/core/src/tracing/trace.ts, packages/core/src/utils/get-default-export.ts, packages/core/src/utils/url.ts, packages/core/test/lib/integrations/express/utils.test.ts, packages/core/test/lib/utils/get-default-export.test.ts, packages/core/test/lib/utils/url.test.ts, packages/node-core/src/index.ts, packages/node-core/src/integrations/http/SentryHttpInstrumentation.ts, packages/node-core/src/integrations/http/httpServerIntegration.ts, packages/node-core/src/integrations/http/httpServerSpansIntegration.ts, packages/node-core/src/integrations/http/index.ts, packages/node-core/src/light/asyncLocalStorageStrategy.ts, packages/node-core/src/light/integrations/httpIntegration.ts, packages/node-core/src/utils/outgoingHttpRequest.ts, packages/node/src/integrations/http.ts, packages/node/src/integrations/tracing/index.ts Sample coverage paths: ./mute.js, /Users/isaacs/dev/js/events-to-array/etoa.js, /home/runner/work/sentry-javascript/sentry-javascript/packages/browser/src/client.ts This usually indicates a path format mismatch between your coverage tool and the repository.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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: 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/

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

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/

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

8 skipped 22 passed (12.0s)

7 skipped 23 passed (11.1s)

7 skipped 23 passed (10.4s)

5 skipped 25 passed (11.4s)

4 skipped 26 passed (18.1s)

1 skipped 29 passed (19.5s)

5 skipped 25 passed (16.9s)

477 skipped 191 passed (37.9s)

343 skipped 325 passed (1.5m)

341 skipped 327 passed (1.5m)

478 skipped 190 passed (38.6s)

1 skipped 14 passed (26.0s)

473 skipped 195 passed (40.6s)

3 skipped 164 passed (2.5m)

4 passed (2.2s)

4 passed (2.2s)

1 failed [chromium] › tests/server.test.ts:120:5 › Should record spans from http instrumentation ──────── 3 passed (4.4s)

1 passed (4.3s)

4 passed (2.6s)

4 passed (4.3s)

4 passed (7.2s)

3 passed (4.2s)

8 passed (2.3s)

3 passed (3.3s)

2 passed (4.4s)

4 passed (7.2s)

3 skipped 17 passed (2.7s)

3 passed (2.5s)

11 passed (2.5s)

5 passed (7.3s)

9 passed (8.6s)

13 passed (12.4s)

10 passed (10.4s)

3 passed (3.4s)

15 passed (10.3s)

3 passed (2.5s)

3 passed (2.4s)

10 passed (5.1s)

10 passed (5.5s)

5 passed (8.1s)

4 passed (7.0s)

3 passed (3.3s)

3 passed (14.5s)

4 passed (2.3s)

1 passed (4.3s)

247 skipped 421 passed (3.6m)

1 passed (5.2s)

7 passed (8.4s)

3 passed (6.1s)

5 passed (7.9s)

1 passed (2.0s)

5 passed (7.8s)

10 passed (6.0s)

10 passed (6.1s)

9 passed (10.9s)

1 passed (6.2s)

12 passed (7.8s)

12 passed (6.8s)

1 passed (5.0s)

2 failed [chromium] › tests/spans.test.ts:128:5 › Sends streamed spans (http.server and manual with Sentry.startSpan) [chromium] › tests/spans.test.ts:179:5 › OTel span appears as child of Sentry span (interop) ───

3 skipped 17 passed (1.9s)

5 passed (11.1s)

8 passed (3.2s)

8 passed (3.2s)

5 passed (8.8s)

5 passed (7.8s)

2 passed (4.2s)

7 passed (13.4s)

7 passed (6.3s)

10 passed (26.5s)

3 passed (13.7s)

1 passed (3.4s)

22 passed (8.7s)

12 passed (6.7s)

3 passed (7.1s)

16 passed (28.5s)

13 passed (28.3s)

1 passed (3.3s)

1 passed (3.4s)

9 passed (11.2s)

10 passed (27.5s)

12 passed (6.5s)

2 passed (3.4s)

3 passed (5.1s)

8 passed (6.1s)

3 passed (2.9s)

24 passed (16.3s)

16 passed (23.1s)

10 passed (26.5s)

11 passed (6.2s)

11 passed (6.5s)

7 passed (4.8s)

8 passed (6.9s)

4 passed (10.9s)

1 skipped 14 passed (12.6s)

4 passed (15.3s)

4 passed (3.8s)

4 passed (7.8s)

5 passed (18.5s)

14 passed (25.2s)

5 passed (7.4s)

9 passed (10.6s)

2 skipped 19 passed (22.7s)

10 passed (36.4s)

3 passed (18.5s)

7 passed (9.3s)

3 passed (6.2s)

5 passed (8.0s)

13 passed (26.0s)

9 passed (11.5s)

9 passed (10.8s)

1 skipped 166 passed (2.5m)

3 skipped 21 passed (19.9s)

12 passed (27.4s)

11 passed (15.6s)

3 passed (6.0s)

251 skipped 417 passed (4.5m)

1 failed [chromium] › tests/request-instrumentation.test.ts:4:5 › Should send a transaction with a fetch span 12 passed (8.6s)

18 passed (21.3s)

12 passed (18.3s)

4 passed (7.2s)

12 passed (27.4s)

1 failed [chromium] › tests/request-instrumentation.test.ts:4:5 › Should send a transaction with a fetch span 12 passed (9.8s)

29 passed (30.5s)

3 passed (18.5s)

3 passed (9.5s)

3 passed (17.8s)

3 passed (9.4s)

40 passed (20.6s)

2 skipped 19 passed (22.4s)

18 passed (18.2s)

9 passed (9.5s)

40 passed (19.8s)

11 passed (4.0s)

11 passed (4.2s)

9 passed (9.3s)

12 passed (27.4s)

4 passed (9.2s)

11 passed (13.8s)

8 passed (28.6s)

15 passed (19.8s)

12 passed (27.9s)

23 passed (12.9s)

14 skipped 12 passed (22.1s)

14 skipped 12 passed (22.0s)

14 skipped 12 passed (21.4s)

11 passed (19.2s)

8 passed (29.9s)

4 passed (10.3s)

12 passed (28.0s)

9 passed (9.7s)

256 skipped 412 passed (4.5m)

12 passed (28.2s)

8 passed (10.1s)

12 passed (8.0s)

1 failed [chromium] › tests/request-instrumentation.test.ts:4:5 › Should send a transaction with a fetch span 12 passed (8.8s)

3 skipped 27 passed (38.9s)

30 passed (12.1s)

4 passed (35.4s)

4 passed (7.5s)

5 skipped 162 passed (4.7m)

4 skipped 10 passed (26.0s)

4 skipped 10 passed (6.9s)

3 passed (29.8s)

3 passed (9.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)

5 passed (41.1s)

5 passed (10.4s)

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

3 passed (3.3s)

115 skipped 553 passed (5.4m)

3 skipped 27 passed (40.8s)

30 passed (13.1s)

4 failed [chromium] › tests/layer.test.ts:6:7 › Lambda layer › tracing in CJS works ───────────────────── [chromium] › tests/layer.test.ts:74:7 › Lambda layer › tracing in ESM works ──────────────────── [chromium] › tests/npm.test.ts:6:7 › NPM package › tracing in CJS works ──────────────────────── [chromium] › tests/npm.test.ts:74:7 › NPM package › tracing in ESM works ─────────────────────── 3 passed (1.8m)

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)

4 skipped 10 passed (35.2s)

2 skipped 12 passed (6.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)

4 skipped 10 passed (29.1s)

2 skipped 12 passed (6.4s)

17 passed (57.2s)

120 skipped 548 passed (5.4m)

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

3 passed (6.8s)

115 skipped 553 passed (5.4m)

4 failed [chromium] › tests/layer.test.ts:6:7 › Lambda layer › tracing in CJS works ───────────────────── [chromium] › tests/layer.test.ts:74:7 › Lambda layer › tracing in ESM works ──────────────────── [chromium] › tests/npm.test.ts:6:7 › NPM package › tracing in CJS works ──────────────────────── [chromium] › tests/npm.test.ts:74:7 › NPM package › tracing in ESM works ─────────────────────── 3 passed (1.7m)

4 failed [chromium] › tests/layer.test.ts:6:7 › Lambda layer › tracing in CJS works ───────────────────── [chromium] › tests/layer.test.ts:74:7 › Lambda layer › tracing in ESM works ──────────────────── [chromium] › tests/npm.test.ts:6:7 › NPM package › tracing in CJS works ──────────────────────── [chromium] › tests/npm.test.ts:74:7 › NPM package › tracing in ESM works ─────────────────────── 3 passed (1.6m)

117 skipped 551 passed (5.3m)

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)

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)

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 passed (19.3s)

2 skipped 48 passed (1.0m)

2 skipped 29 passed (1.1m)

2 skipped 29 passed (36.6s)

4 passed (19.4s)

51 passed (1.0m)

4 passed (19.9s)

51 passed (1.0m)

3 skipped 164 passed (4.5m)

43 passed (2.2m)

2 skipped 29 passed (2.0m)

2 skipped 29 passed (36.4s)

120 skipped 548 passed (5.4m)

5 skipped 29 passed (2.0m)

6 skipped 28 passed (1.0m)

2 skipped 29 passed (2.0m)

2 skipped 29 passed (37.7s)

2 skipped 32 passed (2.6m)

2 skipped 32 passed (1.1m)

2 skipped 32 passed (3.0m)

2 skipped 32 passed (1.1m)