Executing automated changes #11
test.yml
on: push
Test with no Gemfile
21s
Test rubygems: version upgrades RubyGems to that version if the default is older
24s
Test rubygems: version noops if the default is newer
7s
Test rubygems: version uses the Bundler installed by the rubygems update
9s
Test bundler: 1.x for old Ruby
1d 0h
Test with a major Bundler version
22s
Test with a minor Bundler version
24s
Test with an exact Bundler version
21s
Test with a Bundler pre/rc version
20s
Test BUNDLED WITH Bundler dev
6s
Test gemfile depending on Bundler 1
22s
Test installing a Gemfile with nokogiri on TruffleRuby
4s
Test windows-toolchain: none
11s
lint
1d 0h
Matrix: test
Matrix: testGemfileMatrix
Matrix: testLatestRubygemsVersion
Annotations
101 errors and 203 warnings
|
Test installing a Gemfile with nokogiri on TruffleRuby
Error: Unavailable version head for truffleruby on ubuntu-24.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
ubuntu-24.04 truffleruby+graalvm-head
Error: Unavailable version head for truffleruby+graalvm on ubuntu-24.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
ubuntu-22.04 jruby-head
Error: Unavailable version head for jruby on ubuntu-22.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
ubuntu-22.04 truffleruby-head
Error: Unavailable version head for truffleruby on ubuntu-22.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
ubuntu-24.04 jruby-head
Error: Unavailable version head for jruby on ubuntu-24.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
ubuntu-24.04 truffleruby-head
Error: Unavailable version head for truffleruby on ubuntu-24.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
ubuntu-22.04 ruby-head
Error: Unavailable version head for ruby on ubuntu-22.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
ubuntu-24.04 ruby-head
Error: Unavailable version head for ruby on ubuntu-24.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
Test BUNDLED WITH Bundler dev
Error: Unavailable version head for ruby on ubuntu-24.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
ubuntu-22.04 truffleruby+graalvm-head
Error: Unavailable version head for truffleruby+graalvm on ubuntu-22.04
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /home/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/home/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
macos-14 jruby-head
Error: Unavailable version head for jruby on macos-14
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /Users/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/Users/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
macos-14 ruby-head
Error: Unavailable version head for ruby on macos-14
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /Users/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/Users/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
macos-14 truffleruby-head
Error: Unavailable version head for truffleruby on macos-14
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /Users/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/Users/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
macos-14 truffleruby+graalvm-head
Error: Unavailable version head for truffleruby+graalvm on macos-14
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at /Users/runner/work/setup-ruby/setup-ruby/dist/index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (/Users/runner/work/setup-ruby/setup-ruby/dist/index.js:395:14)
|
|
Test rubygems: latest on 3.0
The process '/opt/hostedtoolcache/Ruby/3.0.7/x64/bin/gem' failed with exit code 1
|
|
Test windows-toolchain: none
The current runner (windows-2025-x64) was detected as self-hosted because the platform does not match a GitHub-hosted runner image (or that image is deprecated and no longer supported).
In such a case, you should install Ruby in the $RUNNER_TOOL_CACHE yourself, for example using https://github.com/rbenv/ruby-build
You can take inspiration from this workflow for more details: https://github.com/ruby/ruby-builder/blob/master/.github/workflows/build.yml
$ ruby-build 2.7 C:\hostedtoolcache\windows\Ruby\2.7\x64
Once that completes successfully, mark it as complete with:
$ touch C:\hostedtoolcache\windows\Ruby\2.7\x64.complete
It is your responsibility to ensure installing Ruby like that is not done in parallel.
|
|
Test with rails6 gemfile
Process completed with exit code 1.
|
|
windows-2022 jruby-head
Error: Unavailable version head for jruby on windows-2022
You can request it at https://github.com/ruby/setup-ruby/issues
Cause: Unexpected HTTP response: 404
at D:\a\setup-ruby\setup-ruby\dist\index.js:65032:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async body (D:\a\setup-ruby\setup-ruby\dist\index.js:395:14)
|
|
windows-2022 3.1
The process 'C:\hostedtoolcache\windows\Ruby\3.1.6\x64\bin\bundle.bat' failed with exit code 1
|
|
windows-2022 mingw
Process completed with exit code 1.
|
|
windows-2022 ucrt
Process completed with exit code 1.
|
|
windows-2022 mswin
Process completed with exit code 1.
|
|
Test bundler: 1.x for old Ruby
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
lint
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 2.3
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 jruby
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 truffleruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 3.3
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 truffleruby+graalvm
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 3.0
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 ruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 3.3
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 2.4
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 jruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 1.9
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 2.7
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 1.9
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 2.0
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 2.6
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 2.2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 3.1
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 3.2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 truffleruby+graalvm-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 truffleruby+graalvm-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 2.5
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 2.6
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 2.0
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 truffleruby
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 1.9
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 2.1
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 truffleruby+graalvm
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 truffleruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 jruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 truffleruby+graalvm-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 3.1
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 ruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 3.2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 2.7
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 jruby
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 3.0
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 2.7
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 truffleruby
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 2.0
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 2.3
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 3.1
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 3.2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 jruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 2.2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 2.4
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 jruby
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 2.5
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 mswin
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 2.5
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 2.3
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 2.1
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 jruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 jruby
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 2.2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 2.6
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 3.0
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 truffleruby+graalvm
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 2.4
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 ruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 2.6
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 2.4
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 2.2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 3.2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
ubuntu-20.04 2.0
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 2.3
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 3.0
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 3.1
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 ruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 3.3
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 truffleruby
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-12 2.5
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 3.3
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 mingw
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 2.1
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
macos-13 truffleruby-head
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 2.7
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
windows-2019 2.1
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Test installing a Gemfile with nokogiri on TruffleRuby
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 truffleruby+graalvm-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 jruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 truffleruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 jruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 truffleruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 ruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 ruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test BUNDLED WITH Bundler dev
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 truffleruby+graalvm-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 jruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 ruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 truffleruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 truffleruby+graalvm-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test rubygems: version noops if the default is newer
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test rubygems: latest on 3.2
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test rubygems: latest on 3.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test rubygems: version uses the Bundler installed by the rubygems update
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test rubygems: latest on 2.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test windows-toolchain: none
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 3.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 3.0
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0L13qaQAAAADcF4vbG0f3Tord4s4ZLrXgUEhMMzBFREdFMDQxMABFZGdl
|
|
ubuntu-24.04 3.0
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 3.2
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 3.2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Ll3qaQAAAAAYx+okyhYZR4pzMu3y1vmUQ0hJMzBFREdFMDQwOQBFZGdl
|
|
ubuntu-22.04 3.2
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 3.1
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 3.1
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0L13qaQAAAAAmJPAfODqzRpB9uwPYxjHZTVNQMzExMDAwMTAxMDM3AEVkZ2U=
|
|
ubuntu-24.04 3.1
Failed to restore: Cache service responded with 400
|
|
Test with a Bundler pre/rc version
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test with an exact Bundler version
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 3.3
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 3.3
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0L13qaQAAAACv44NO//l5QKsXLYYEpWHDTVNQMzExMDAwMTA0MDI5AEVkZ2U=
|
|
ubuntu-22.04 3.3
Failed to restore: Cache service responded with 400
|
|
Test with no Gemfile
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 3.3
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 3.3
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0L13qaQAAAADkQ5pOBJmpSqyN+zLORGNeTVNQMzExMDAwMTA4MDI1AEVkZ2U=
|
|
ubuntu-24.04 3.3
Failed to restore: Cache service responded with 400
|
|
macos-14 3.2
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 3.2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0M13qaQAAAAArfdozwnShTZf82KTM0GowU04xRURHRTE3MTAARWRnZQ==
|
|
macos-14 3.2
Failed to restore: Cache service responded with 400
|
|
Test with a major Bundler version
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test gemfile depending on Bundler 1
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test gemfile depending on Bundler 1
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0O13qaQAAAACsAMpy58AUQ5VIFUtZD9WiUEhMMzBFREdFMDIyMABFZGdl
|
|
Test gemfile depending on Bundler 1
Failed to restore: Cache service responded with 400
|
|
macos-14 3.3
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 3.3
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0M13qaQAAAACd5pl799yzSrA7bZPL8Qc0UEFPRURHRTA1MTkARWRnZQ==
|
|
macos-14 3.3
Failed to restore: Cache service responded with 400
|
|
Test rubygems: latest on 2.5
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test rubygems: latest on 2.6
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test rubygems: version upgrades RubyGems to that version if the default is older
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test with a minor Bundler version
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 2.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 2.0
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NF3qaQAAAAAcVDOCIxu0T5TrxuH9zKexUEhYMzFFREdFMDYyMQBFZGdl
|
|
ubuntu-24.04 2.0
Failed to restore: Cache service responded with 400
|
|
macos-14 3.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 3.0
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NV3qaQAAAACw+qo+mLqwTodiSMAL6zBBU04xRURHRTI5MjEARWRnZQ==
|
|
macos-14 3.0
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 3.2
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 3.2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0MV3qaQAAAADAFoPlqzIlTb+fVSBfwzgpUEFPRURHRTA2MDcARWRnZQ==
|
|
ubuntu-24.04 3.2
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 3.1
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 3.1
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0MV3qaQAAAAAuEsWanl/+TaKeJY2843fcUEFPRURHRTA1MjAARWRnZQ==
|
|
ubuntu-22.04 3.1
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 2.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 2.0
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NF3qaQAAAACbAU1hvyMFQYb380+AEX8YUEhYMzFFREdFMDUwNwBFZGdl
|
|
ubuntu-22.04 2.0
Failed to restore: Cache service responded with 400
|
|
Test rubygems: latest on 2.3
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 3.1
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 3.1
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0N13qaQAAAABiaw9CT2rcR6qpLennBtRUUEFPRURHRTA2MTMARWRnZQ==
|
|
macos-14 3.1
Failed to restore: Cache service responded with 400
|
|
Test rubygems: latest on 2.7
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 3.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 3.0
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NF3qaQAAAABJPSNT/ZxXRLh+iDxlTdnWUEhMMzBFREdFMDQxMQBFZGdl
|
|
ubuntu-22.04 3.0
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 1.9
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 1.9
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0OF3qaQAAAAA6mfvWVRfWR6Vd/6OFnMCxUEhYMzFFREdFMDIxNABFZGdl
|
|
ubuntu-22.04 1.9
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 2.1
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 2.1
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0OF3qaQAAAADZbyfW4li3QZlCDVrNFiK0UEFPRURHRTA1MTEARWRnZQ==
|
|
ubuntu-22.04 2.1
Failed to restore: Cache service responded with 400
|
|
Test with rails6 gemfile
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test with rails6 gemfile
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0R13qaQAAAAD1yWRE3YKCR50sDG2UpBoCUEFPRURHRTA2MTUARWRnZQ==
|
|
Test with rails6 gemfile
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 2.1
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 2.1
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0OF3qaQAAAAAzrSx/X9h2QpLyqNfAEwKNUEFPRURHRTA2MjEARWRnZQ==
|
|
ubuntu-24.04 2.1
Failed to restore: Cache service responded with 400
|
|
windows-2022 jruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test with rails5 gemfile
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test with rails5 gemfile
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0TF3qaQAAAAAXkv+oV/VcQq/cIKKTggptREVOMzAxMDAwMTAxMDE3AEVkZ2U=
|
|
Test with rails5 gemfile
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 truffleruby
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 truffleruby
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0O13qaQAAAAAyoDiZQwKpR43SOldAKSgzTVNQMzExMDAwMTA2MDA5AEVkZ2U=
|
|
ubuntu-24.04 truffleruby
Failed to restore: Cache service responded with 400
|
|
macos-14 truffleruby
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 truffleruby
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Pl3qaQAAAABFovpZemyHS4J9YkGA50ZRUEhMMzBFREdFMDExNABFZGdl
|
|
macos-14 truffleruby
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 truffleruby
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 truffleruby
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Ol3qaQAAAACM3/XkIqpQQrTQdHLmzgfQUEhMMzBFREdFMDIxNwBFZGdl
|
|
ubuntu-22.04 truffleruby
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 2.4
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 2.4
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0PF3qaQAAAACr4oKv/5suQpU5PLKUvKHuUEhMMzBFREdFMDIxMABFZGdl
|
|
ubuntu-22.04 2.4
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 2.4
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 2.4
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0P13qaQAAAAAikITCxrecRLoJzeoKfg5RUEhMMzBFREdFMDEwNwBFZGdl
|
|
ubuntu-24.04 2.4
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 2.5
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 2.5
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Pl3qaQAAAABDLflFwTYTRayijLsDEbOmTVNQMzExMDAwMTAyMDA5AEVkZ2U=
|
|
ubuntu-24.04 2.5
Failed to restore: Cache service responded with 400
|
|
macos-14 2.7
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 2.7
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0QF3qaQAAAADCjDy6u+xUTZc8MsuEpT+YUEhMMzBFREdFMDQxOQBFZGdl
|
|
macos-14 2.7
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 2.5
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 2.5
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Pl3qaQAAAAAVVyOLW32sSrBQYwGg/NxtUEhMMzBFREdFMDEyMgBFZGdl
|
|
ubuntu-22.04 2.5
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 2.6
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 2.6
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0P13qaQAAAAD72CWNPCHyQI+fLVrOhpJ9UEhMMzBFREdFMDIxMABFZGdl
|
|
ubuntu-24.04 2.6
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 2.7
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 2.7
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Pl3qaQAAAABtUlHFrIjDR7S0FzbuoA4SUEhMMzBFREdFMDExNABFZGdl
|
|
ubuntu-24.04 2.7
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 2.3
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 2.3
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0P13qaQAAAABKRqnvGK/hT7FQv3sSZuHEQ0hJMzBFREdFMDQxNQBFZGdl
|
|
ubuntu-22.04 2.3
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 2.6
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 2.6
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0P13qaQAAAABBOwcFoQrxQr8zWt2FntUeUEhYMzFFREdFMDIwNwBFZGdl
|
|
ubuntu-22.04 2.6
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 2.7
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 2.7
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0P13qaQAAAABjUdUXtcQFQKr7gHNAc7CLREVOMzAxMDAwMTAyMDUzAEVkZ2U=
|
|
ubuntu-22.04 2.7
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 2.3
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 2.3
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Pl3qaQAAAAC6wtYeLfs9TKL6/0fmlozjUEFPRURHRTA2MTMARWRnZQ==
|
|
ubuntu-24.04 2.3
Failed to restore: Cache service responded with 400
|
|
windows-2022 3.1
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 2.6
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 2.6
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0S13qaQAAAACopqkHR1zNSLxrA/8uIT5tU04xRURHRTE2MTAARWRnZQ==
|
|
macos-14 2.6
Failed to restore: Cache service responded with 400
|
|
macos-14 jruby
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 jruby
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0PV3qaQAAAACjeI1SNQOPSLFXInyVAi03UEhMMzBFREdFMDExNABFZGdl
|
|
macos-14 jruby
Failed to restore: Cache service responded with 400
|
|
windows-2022 2.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 2.0
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0VF3qaQAAAACuHU529igfSIVeMl256TmoREVOMzAxMDAwMTA0MDUzAEVkZ2U=
|
|
windows-2022 2.0
Failed to restore: Cache service responded with 400
|
|
windows-2022 mingw
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 mingw
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0U13qaQAAAAAC+y2vqySzRIIE9YXnG/s9TVNQMzExMDAwMTAzMDQ5AEVkZ2U=
|
|
windows-2022 mingw
Failed to restore: Cache service responded with 400
|
|
windows-2022 ucrt
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 ucrt
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0VV3qaQAAAABPNHpddf0ASLSvmnRvOEcnUEhMMzBFREdFMDExNABFZGdl
|
|
windows-2022 ucrt
Failed to restore: Cache service responded with 400
|
|
windows-2022 ruby-head
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 ruby-head
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0VF3qaQAAAABUqMIysWXLQa2tk4ZqHU4qQ0hJMzBFREdFMDIxMwBFZGdl
|
|
windows-2022 ruby-head
Failed to restore: Cache service responded with 400
|
|
windows-2022 mswin
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 mswin
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YF3qaQAAAAAIVDBOI8LlRrIfs7AbX/C/TVNQMzExMDAwMTA3MDM3AEVkZ2U=
|
|
windows-2022 mswin
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 jruby
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 jruby
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Pl3qaQAAAADz2zNNSEZFTqhzUoYqaWw3UEhMMzBFREdFMDQyMABFZGdl
|
|
ubuntu-24.04 jruby
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 jruby
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 jruby
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0QF3qaQAAAACypj/yP2l8Rrd0bKwpbiVoREVOMzAxMDAwMTA3MDQ1AEVkZ2U=
|
|
ubuntu-22.04 jruby
Failed to restore: Cache service responded with 400
|
|
windows-2022 2.1
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 2.1
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YF3qaQAAAAAw1fTNNg/8Q4aFHM52wFgUREVOMzAxMDAwMTA3MDIxAEVkZ2U=
|
|
windows-2022 2.1
Failed to restore: Cache service responded with 400
|
|
windows-2022 3.0
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 3.0
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0al3qaQAAAABosLwIh7veRJYwt3GzpxwDTVNQMzExMDAwMTA2MDQ5AEVkZ2U=
|
|
windows-2022 3.0
Failed to restore: Cache service responded with 400
|
|
windows-2022 3.2
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 3.2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0bl3qaQAAAAAd2xFIYSXPR70s20A8BuTuUEhYMzFFREdFMDIxMQBFZGdl
|
|
windows-2022 3.2
Failed to restore: Cache service responded with 400
|
|
windows-2022 2.3
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 2.3
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0aF3qaQAAAACJ0mGVN0ikRqWTLYZtryU4Q0hHRURHRTE4MTcARWRnZQ==
|
|
windows-2022 2.3
Failed to restore: Cache service responded with 400
|
|
windows-2022 2.2
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 2.2
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0dF3qaQAAAABJghA7AKHOQ4JUFrCDchdDQ0hHRURHRTE4MTAARWRnZQ==
|
|
windows-2022 2.2
Failed to restore: Cache service responded with 400
|
|
windows-2022 2.4
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 2.4
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0cl3qaQAAAAA9uJo7GW1mR4JUYt5gU1ZZUEhYMzFFREdFMDYyMABFZGdl
|
|
windows-2022 2.4
Failed to restore: Cache service responded with 400
|
|
windows-2022 3.3
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 3.3
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0nV3qaQAAAADvn1UMKoYbRLxJSiPBjhSsQ0hJMzBFREdFMDExOQBFZGdl
|
|
windows-2022 3.3
Failed to restore: Cache service responded with 400
|
|
macos-14 truffleruby+graalvm
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-14 truffleruby+graalvm
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YF3qaQAAAAA7tqD16vcVS7VJRj1JMZtzU04xRURHRTIwMTQARWRnZQ==
|
|
macos-14 truffleruby+graalvm
Failed to restore: Cache service responded with 400
|
|
windows-2022 2.7
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 2.7
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0il3qaQAAAABSKqAINGFYQLeRLnCobPe0TVNQMzExMDAwMTAxMDUzAEVkZ2U=
|
|
windows-2022 2.7
Failed to restore: Cache service responded with 400
|
|
windows-2022 2.6
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 2.6
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0jV3qaQAAAADyGGiqNdIWRKkVLVxmyS+JUEhMMzBFREdFMDExMwBFZGdl
|
|
windows-2022 2.6
Failed to restore: Cache service responded with 400
|
|
windows-2022 2.5
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 2.5
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ll3qaQAAAACD+gFjJ4E8SK2wuhX9cjHtUEhMMzBFREdFMDIwNgBFZGdl
|
|
windows-2022 2.5
Failed to restore: Cache service responded with 400
|
|
ubuntu-22.04 truffleruby+graalvm
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-22.04 truffleruby+graalvm
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Z13qaQAAAACO3mGbnqIYSrdALwOclbf3UEhMMzBFREdFMDQxNwBFZGdl
|
|
ubuntu-22.04 truffleruby+graalvm
Failed to restore: Cache service responded with 400
|
|
ubuntu-24.04 truffleruby+graalvm
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-24.04 truffleruby+graalvm
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Z13qaQAAAAA1Bia2OAC4QpkKKJ4NxqaaUEhMMzBFREdFMDQxMgBFZGdl
|
|
ubuntu-24.04 truffleruby+graalvm
Failed to restore: Cache service responded with 400
|
|
windows-2022 jruby
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 will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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-2022 jruby
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Xl3qaQAAAAA/KbW0V7glS4nHUeESPquHUEhMMzBFREdFMDIxNgBFZGdl
|
|
windows-2022 jruby
Failed to restore: Cache service responded with 400
|