Collect code coverage for rubygems and bundler #11809
hsbtbundler.yml
on: pull_request
Matrix: bundler
All bundler jobs pass
4s
Annotations
38 errors and 19 warnings
|
Bundler on Windows (ruby-3.3)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (ruby-3.3)
The operation was canceled.
|
|
Bundler on Ubuntu (ruby-3.4)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Ubuntu (ruby-3.4)
The operation was canceled.
|
|
Bundler on Ubuntu (ruby-3.3)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Ubuntu (ruby-3.3)
The operation was canceled.
|
|
Bundler on Windows (ruby-3.3)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (ruby-3.3)
The operation was canceled.
|
|
Bundler on Ubuntu (ruby-3.2)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Ubuntu (ruby-3.2)
The operation was canceled.
|
|
Bundler on Windows (ruby-3.4)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (ruby-3.4)
The operation was canceled.
|
|
Bundler on Ubuntu (ruby-4.0 (psych))
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Ubuntu (ruby-4.0 (psych))
The operation was canceled.
|
|
Bundler on Windows (ruby-3.4)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (ruby-3.4)
The operation was canceled.
|
|
Bundler on Ubuntu (ruby-4.0)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Ubuntu (ruby-4.0)
The operation was canceled.
|
|
Bundler on Ubuntu (jruby)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Ubuntu (jruby)
The operation was canceled.
|
|
Bundler on Windows (ruby-3.3)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (ruby-3.3)
The operation was canceled.
|
|
Bundler on Windows (ruby-3.4)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (ruby-3.4)
The operation was canceled.
|
|
Bundler on Windows (ruby-3.4)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (ruby-3.4)
The operation was canceled.
|
|
Bundler on Windows (ruby-3.3)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (ruby-3.3)
The operation was canceled.
|
|
Bundler on macOS (ruby-3.4)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on macOS (ruby-3.4)
The operation was canceled.
|
|
Bundler on macOS (ruby-3.2)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on macOS (ruby-3.2)
The operation was canceled.
|
|
Bundler on macOS (ruby-3.3)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on macOS (ruby-3.3)
The operation was canceled.
|
|
Bundler on macOS (ruby-4.0)
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on macOS (ruby-4.0)
The operation was canceled.
|
|
All bundler jobs pass
Process completed with exit code 1.
|
|
bundler
Canceling since a higher priority waiting request for ci-refs/pull/9394/merge-bundler exists
|
|
Bundler on Windows (jruby)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Windows (ruby-3.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Ubuntu (ruby-3.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Ubuntu (ruby-3.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Windows (ruby-3.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Ubuntu (ruby-3.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Windows (ruby-3.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Ubuntu (ruby-4.0 (psych))
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Windows (ruby-3.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Ubuntu (ruby-4.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Ubuntu (jruby)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Windows (ruby-3.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Windows (ruby-3.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Windows (ruby-3.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on Windows (ruby-3.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on macOS (ruby-3.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on macOS (ruby-3.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on macOS (ruby-3.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bundler on macOS (ruby-4.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|