Release ruby.wasm #109
kateinoigakukunrelease.yml
on: schedule
create-tag
8s
release-nightly-npm-packages
/
build-rake-task-matrix
25s
release-nightly-npm-packages
/
lint
release-tag-js-gem
release-tag-npm-packages
/
lint
release-tag-ruby_wasm-gem
/
Push source gem
Matrix: release-nightly-npm-packages / build-builder-image
Matrix: release-tag-npm-packages / build-builder-image
Waiting for pending jobs
Matrix: release-nightly-npm-packages / rake-tasks
Matrix: release-tag-npm-packages / rake-tasks
Waiting for pending jobs
Matrix: release-tag-ruby_wasm-gem / cross-gem
Waiting for pending jobs
release-nightly-npm-packages
/
release-artifacts
1m 54s
release-tag-npm-packages
/
release-artifacts
Annotations
27 warnings
|
release-nightly-npm-packages / build-builder-image (wasm32-unknown-emscripten)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / build-builder-image (wasm32-unknown-wasip1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.3-wasm32-unknown-emscripten-full, rubies/ruby-3.3-wasm32-unknown-emscripten-f...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:4.0-wasm32-unknown-emscripten-full, rubies/ruby-4.0-wasm32-unknown-emscripten-f...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.2-wasm32-unknown-emscripten-full, rubies/ruby-3.2-wasm32-unknown-emscripten-f...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:4.0-wasm32-unknown-wasip1-full, rubies/ruby-4.0-wasm32-unknown-wasip1-full.tar....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.4-wasm32-unknown-emscripten-full, rubies/ruby-3.4-wasm32-unknown-emscripten-f...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.3-wasm32-unknown-wasip1-minimal, rubies/ruby-3.3-wasm32-unknown-wasip1-minima...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.2-wasm32-unknown-wasip1-full, rubies/ruby-3.2-wasm32-unknown-wasip1-full.tar....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:4.0-wasm32-unknown-wasip1-minimal, rubies/ruby-4.0-wasm32-unknown-wasip1-minima...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.4-wasm32-unknown-wasip1-full, rubies/ruby-3.4-wasm32-unknown-wasip1-full.tar....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.2-wasm32-unknown-wasip1-minimal, rubies/ruby-3.2-wasm32-unknown-wasip1-minima...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (npm:ruby-wasm-wasi, npm:configure_prerelease, packages/npm-packages/ruby-wasm-wasi/ru...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.3-wasm32-unknown-wasip1-full, rubies/ruby-3.3-wasm32-unknown-wasip1-full.tar....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:3.4-wasm32-unknown-wasip1-minimal, rubies/ruby-3.4-wasm32-unknown-wasip1-minima...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:head-wasm32-unknown-wasip1-minimal, rubies/ruby-head-wasm32-unknown-wasip1-mini...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (npm:ruby-3.2-wasm-wasi, npm:configure_prerelease, packages/npm-packages/ruby-3.2-wasm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:head-wasm32-unknown-wasip1-full, rubies/ruby-head-wasm32-unknown-wasip1-full.ta...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (standalone:irb, packages/standalone/irb/dist, standalone-irb, wasm32-unknown-wasip1, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (npm:ruby-4.0-wasm-wasi, npm:configure_prerelease, packages/npm-packages/ruby-4.0-wasm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (npm:ruby-3.3-wasm-wasi, npm:configure_prerelease, packages/npm-packages/ruby-3.3-wasm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (standalone:ruby, packages/standalone/ruby/dist, standalone-ruby, wasm32-unknown-wasip...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (npm:ruby-head-wasm-wasi, npm:configure_prerelease, packages/npm-packages/ruby-head-wa...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (npm:ruby-3.4-wasm-wasi, npm:configure_prerelease, packages/npm-packages/ruby-3.4-wasm...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (npm:ruby-head-wasm-emscripten, npm:configure_prerelease, packages/npm-packages/ruby-h...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (build:head-wasm32-unknown-emscripten-full, rubies/ruby-head-wasm32-unknown-emscripten...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-nightly-npm-packages / rake-tasks (npm:ruby-head-wasm-wasip2, npm:configure_prerelease, packages/npm-packages/ruby-head-...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-manifest
|
221 Bytes |
sha256:4bec8b1783218cc7207ac51cd60da279e6bd4caaac5cb87e672f3f37d66115f3
|
|
|
npm-ruby-3.2-wasm-wasi
|
29.3 MB |
sha256:40729b58fb975acd384cbff21f4051bcb9f55bf69b962e4ef2eac61f269fc22d
|
|
|
npm-ruby-3.3-wasm-wasi
|
32 MB |
sha256:413ccb04c8a34c1aa63cd47ab92469c29f23e50f37e64be4f0b3af1dc6a49bb1
|
|
|
npm-ruby-3.4-wasm-wasi
|
28.4 MB |
sha256:569c0aaaf7d582b302de3c6eae0b557ecac0c72e5f6e2a4bcb84073035871703
|
|
|
npm-ruby-4.0-wasm-wasi
|
31.3 MB |
sha256:6eca63a8c67aab03844cfc7d76c41a66c7505f2238762de3e675fab7c18a3276
|
|
|
npm-ruby-head-wasm-emscripten
|
9.98 MB |
sha256:38431be48d31cf71136f6484754d63d551bfd8cf8e14a03e7b7260a432559aca
|
|
|
npm-ruby-head-wasm-wasi
|
31.7 MB |
sha256:507c157a22c30bc3f06addb7c96d88b43bdb5e426ea3b5df24b664fad95ba5e7
|
|
|
npm-ruby-head-wasm-wasip2
|
22.4 MB |
sha256:1dd2e798a24a2232faf18b966e6bb1949b7415914d673d40303b3308b0dcd604
|
|
|
npm-ruby-wasm-wasi
|
82.4 KB |
sha256:1d749267b27f56094c78fafc96055f6cf8db37942205776c0d5c386a15d37051
|
|
|
ruby-3.2-wasm32-unknown-emscripten-full
|
11.6 MB |
sha256:c805926056468cf5917125559bbacc5f541e12f215f5782786da574966c1973d
|
|
|
ruby-3.2-wasm32-unknown-wasip1-full
|
22 MB |
sha256:ec76489fafc3efc9ed24018fdc86aebcea6eec348fceb4cca52fe00f4bb2ab3e
|
|
|
ruby-3.2-wasm32-unknown-wasip1-minimal
|
18.9 MB |
sha256:9ac4f28f89dcd238c37eb3d6fcd963d3791e478c8e8e0406408d91d22ec9272e
|
|
|
ruby-3.3-wasm32-unknown-emscripten-full
|
12.4 MB |
sha256:d5db8d71f24c1ae01b58419f015f3821adb3910c90cce99bf7eff0a89fb2968f
|
|
|
ruby-3.3-wasm32-unknown-wasip1-full
|
24.8 MB |
sha256:34fe896396437833d2f69e4d72de4fcd40ef372762da3940f8200000807d28eb
|
|
|
ruby-3.3-wasm32-unknown-wasip1-minimal
|
21.8 MB |
sha256:5c7a04cf8377eb4ca16283d14b6cabc37ed9148b83b299aa84121a2f1ad9ad6a
|
|
|
ruby-3.4-wasm32-unknown-emscripten-full
|
10.6 MB |
sha256:ebc301d134512262fc7cbde92eb3b56870f220a4d0efaf3450e9f9d4be952c09
|
|
|
ruby-3.4-wasm32-unknown-wasip1-full
|
23.8 MB |
sha256:22f24ecff459c6df80dc65afb9ef2511c3c56b0e70766c3b87e20cc65f560236
|
|
|
ruby-3.4-wasm32-unknown-wasip1-minimal
|
21 MB |
sha256:5bc33df698baba9b9e04a64889dfb8471cb5aba18c8aa5c41d60f8db3ad5d0a3
|
|
|
ruby-4.0-wasm32-unknown-emscripten-full
|
11.8 MB |
sha256:06211d447c04e95f8e03bf0ce6492e1e5032057c1a37709fa1eda9cb32be0b37
|
|
|
ruby-4.0-wasm32-unknown-wasip1-full
|
26.1 MB |
sha256:dca3999542a2153effd56e0baa0a1eec202098ec075014d380327203524fa505
|
|
|
ruby-4.0-wasm32-unknown-wasip1-minimal
|
23.2 MB |
sha256:2eb53b362f769eb95cb15314e8aa89b9669512844a2ebcc799dd6f71267af29d
|
|
|
ruby-head-wasm32-unknown-emscripten-full
|
12 MB |
sha256:6bed86a2d0d7f48c12bdb9842e4994aa99603e86e2e8deccaa8bee03fdcb53eb
|
|
|
ruby-head-wasm32-unknown-wasip1-full
|
26.4 MB |
sha256:b4a8b3d78e18c44e4ed6b6d9bdfacd9fdb85d0da49e3cf573e09cf5d558b1920
|
|
|
ruby-head-wasm32-unknown-wasip1-minimal
|
23.4 MB |
sha256:e3b6595536105f9dac4cb1e935d684b07fdc129e8aa0b49fb14d335960688d3c
|
|
|
standalone-irb
|
32.3 MB |
sha256:40568f26ed79a7e9fafbc95843a885944ef2bd7075b555e0a820bf7529cc78b6
|
|
|
standalone-ruby
|
32 MB |
sha256:c39a677974981f4f60ae5ac2c4373de807b3dbbea4d51b45c777627f45ad4652
|
|