Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

AssertionError: expected '> test\r\n> vitest run\r\n\r\n[rolldo…' to contain '✓ test/math.test.ts' - Expected + Received - ✓ test/math.test.ts + > test + > vitest run + + [rolldown] Downloading @rolldown/[email protected] on WebContainer... + Progress: resolved 1, reused 0, downloaded 0, added 0 + Progress: resolved 2, reused 0, downloaded 0, added 0 + Progress: resolved 5, reused 0, downloaded 0, added 0 + Packages: +7 + +++++++ + Progress: resolved 5, reused 0, downloaded 0, added 0 + Progress: resolved 7, reused 0, downloaded 0, added 0 + Progress: resolved 7, reused 0, downloaded 1, added 0 + Progress: resolved 7, reused 0, downloaded 2, added 2 + Progress: resolved 7, reused 0, downloaded 3, added 3 + Progress: resolved 7, reused 0, downloaded 4, added 3 + Progress: resolved 7, reused 0, downloaded 4, added 4 + Progress: resolved 7, reused 0, downloaded 5, added 5 + Progress: resolved 7, reused 0, downloaded 6, added 6 + Progress: resolved 7, reused 0, downloaded 7, added 7, done + + dependencies: + + @rolldown/binding-wasm32-wasi 1.0.0-rc.10 + + Done in 3.7s + (node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time + (Use `node --trace-warnings ...` to show where the warning was created) + + RUN v4.1.0 /home/9u3bpo3trqtttfgv92a5z9imzyea80-t1xe + + (node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time + (Use `node --trace-warnings ...` to show where the warning was created) + + ❯ test/math.test.ts [queued] + + Test Files 0 passed (1) + Tests 0 passed (0) + Start at 20:11:21 + Duration 721ms + ❯ test/math.test.ts (0 test) + + ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ + + FAIL test/math.test.ts [ test/math.test.ts ] + Error: Cannot read properties of undefined (reading 'whenLoaded') + ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯ + + + Test Files 1 failed (1) + Tests no tests + Start at 20:11:21 + Duration 843ms (transform 0ms, setup 0ms, import 0ms, tests 0ms, environment 0ms) + + \ ❯ test/basic.test.ts:12:17

AssertionError: expected '> test\r\n> vitest run\r\n\r\n[rolldo…' to contain '✓ test/math.test.ts' - Expected + Received - ✓ test/math.test.ts + > test + > vitest run + + [rolldown] Downloading @rolldown/[email protected] on WebContainer... + Progress: resolved 1, reused 0, downloaded 0, added 0 + Progress: resolved 2, reused 0, downloaded 0, added 0 + Progress: resolved 5, reused 0, downloaded 0, added 0 + Packages: +7 + +++++++ + Progress: resolved 5, reused 0, downloaded 0, added 0 + Progress: resolved 7, reused 0, downloaded 0, added 0 + Progress: resolved 7, reused 0, downloaded 1, added 0 + Progress: resolved 7, reused 0, downloaded 2, added 2 + Progress: resolved 7, reused 0, downloaded 3, added 3 + Progress: resolved 7, reused 0, downloaded 4, added 3 + Progress: resolved 7, reused 0, downloaded 4, added 4 + Progress: resolved 7, reused 0, downloaded 5, added 5 + Progress: resolved 7, reused 0, downloaded 6, added 6 + Progress: resolved 7, reused 0, downloaded 7, added 7, done + + dependencies: + + @rolldown/binding-wasm32-wasi 1.0.0-rc.10 + + Done in 3.7s + (node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time + (Use `node --trace-warnings ...` to show where the warning was created) + + RUN v4.1.0 /home/9u3bpo3trqtttfgv92a5z9imzyea80-t1xe + + (node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time + (Use `node --trace-warnings ...` to show where the warning was created) + + ❯ test/math.test.ts [queued] + + Test Files 0 passed (1) + Tests 0 passed (0) + Start at 20:11:21 + Duration 721ms + ❯ test/math.test.ts (0 test) + + ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ + + FAIL test/math.test.ts [ test/math.test.ts ] + Error: Cannot read properties of undefined (reading 'whenLoaded') + ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯ + + + Test Files 1 failed (1) + Tests no tests + Start at 20:11:21 + Duration 843ms (transform 0ms, setup 0ms, import 0ms, tests 0ms, environment 0ms) + + \ ❯ test/basic.test.ts:12:17

Process completed with exit code 1.

Process completed with exit code 1.

(FiberFailure) ReferenceError: localStorage is not defined ❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67 ❯ packages/platform/src/internal/keyValueStore.ts:260:21 ❯ packages/effect/src/internal/layer.ts:1035:62 ❯ packages/effect/src/internal/fiberRuntime.ts:1161:41 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { _id: 'FiberFailure' }

(FiberFailure) ReferenceError: localStorage is not defined ❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67 ❯ packages/platform/src/internal/keyValueStore.ts:260:21 ❯ packages/effect/src/internal/layer.ts:1035:62 ❯ packages/effect/src/internal/fiberRuntime.ts:1161:41 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { _id: 'FiberFailure' }

(FiberFailure) ReferenceError: localStorage is not defined ❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67 ❯ packages/platform/src/internal/keyValueStore.ts:260:21 ❯ packages/effect/src/internal/layer.ts:1035:62 ❯ packages/effect/src/internal/fiberRuntime.ts:1161:41 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { _id: 'FiberFailure' }

(FiberFailure) ReferenceError: localStorage is not defined ❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67 ❯ packages/platform/src/internal/keyValueStore.ts:260:21 ❯ packages/effect/src/internal/layer.ts:1035:62 ❯ packages/effect/src/internal/fiberRuntime.ts:1161:41 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { _id: 'FiberFailure' }

(FiberFailure) ReferenceError: localStorage is not defined ❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67 ❯ packages/platform/src/internal/keyValueStore.ts:260:21 ❯ packages/effect/src/internal/layer.ts:1035:62 ❯ packages/effect/src/internal/fiberRuntime.ts:1161:41 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { _id: 'FiberFailure' }

(FiberFailure) ReferenceError: localStorage is not defined ❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67 ❯ packages/platform/src/internal/keyValueStore.ts:260:21 ❯ packages/effect/src/internal/layer.ts:1035:62 ❯ packages/effect/src/internal/fiberRuntime.ts:1161:41 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { _id: 'FiberFailure' }

(FiberFailure) ReferenceError: localStorage is not defined ❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67 ❯ packages/platform/src/internal/keyValueStore.ts:260:21 ❯ packages/effect/src/internal/layer.ts:1035:62 ❯ packages/effect/src/internal/fiberRuntime.ts:1161:41 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { _id: 'FiberFailure' }

AssertionError: expected { _id: 'Cause', …(3) } to strictly equal { Object (_tag, left, ...) } - Expected + Received @@ -1,8 +1,8 @@ { "_id": "Cause", - "_tag": "Parallel", + "_tag": "Sequential", "left": { "_id": "Cause", "_tag": "Empty", }, "right": { ❯ packages/effect/test/assertions.test.ts:64:60

AssertionError: expected { _id: 'Cause', …(3) } to deeply equal { Object (_tag, left, ...) } - Expected + Received @@ -1,8 +1,8 @@ { "_id": "Cause", - "_tag": "Parallel", + "_tag": "Sequential", "left": { "_id": "Cause", "_tag": "Empty", }, "right": { ❯ packages/effect/test/assertions.test.ts:60:60

ReferenceError: it is not defined ❯ Proxy.defineInlineTest node_modules/.pnpm/[email protected]/node_modules/jscodeshift/src/testUtils.js:143:3 ❯ scripts/codemods/ts-fence.test.ts:13:13 ❯ scripts/codemods/ts-fence.test.ts:24:1

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

Unexpected input(s) 'repository', valid inputs are ['app_id', 'github_api_url', 'installation_retrieval_mode', 'installation_retrieval_payload', 'permissions', 'private_key', 'repositories', 'revoke']

Unexpected input(s) 'repository', valid inputs are ['app_id', 'github_api_url', 'installation_retrieval_mode', 'installation_retrieval_payload', 'permissions', 'private_key', 'repositories', 'revoke']

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Unexpected input(s) 'repository', valid inputs are ['app_id', 'github_api_url', 'installation_retrieval_mode', 'installation_retrieval_payload', 'permissions', 'private_key', 'repositories', 'revoke']