Update functionalscript to v0.24.0 and add CI workflow #1
ci.yml
on: pull_request
ubuntu-intel
1m 0s
ubuntu-arm
37s
macos-intel
1m 17s
macos-arm
37s
windows-intel
1m 21s
windows-arm
1m 28s
node24
9s
playwright
1m 9s
Annotations
8 errors, 6 warnings, and 1 notice
|
node24
Process completed with exit code 1.
|
|
macos-arm
Process completed with exit code 1.
|
|
ubuntu-arm
Process completed with exit code 1.
|
|
ubuntu-intel
Process completed with exit code 1.
|
|
playwright
Process completed with exit code 1.
|
|
macos-intel
Process completed with exit code 1.
|
|
windows-intel
Process completed with exit code 1.
|
|
windows-arm
Process completed with exit code 1.
|
|
macos-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: wasmerio/setup-wasmer@v3.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ubuntu-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: wasmerio/setup-wasmer@v3.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ubuntu-intel
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: wasmerio/setup-wasmer@v3.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos-intel
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: wasmerio/setup-wasmer@v3.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-intel
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: wasmerio/setup-wasmer@v3.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-arm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: wasmerio/setup-wasmer@v3.1. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-intel
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|