Add workaround for Ruby 3.1 after RubyGems 3.7.0 release #1562
test.yml
on: pull_request
Test .ruby-version
4s
Test .tool-versions
6s
Test mise.toml
17s
Test with no Gemfile
20s
Test rubygems: version upgrades RubyGems to that version if the default is older
24s
Test rubygems: version noops if the default is newer
6s
Test rubygems: version uses the Bundler installed by the rubygems update
9s
Test bundler: 1.x for old Ruby
21s
Test with a major Bundler version
19s
Test with a minor Bundler version
19s
Test with an exact Bundler version
20s
Test with a Bundler pre/rc version
21s
Test BUNDLED WITH Bundler dev
7s
Test gemfile depending on Bundler 1
23s
Test installing a Gemfile with nokogiri on TruffleRuby
18s
Test windows-toolchain: none
19s
lint
14s
Matrix: test
Matrix: testGemfileMatrix
Matrix: testLatestRubygemsVersion
Annotations
2 errors and 4 warnings
|
windows-2022 3.1
The process 'C:\hostedtoolcache\windows\Ruby\3.1.7\x64\bin\bundle.bat' failed with exit code 1
|
|
windows-2025 3.1
The process 'C:\hostedtoolcache\windows\Ruby\3.1.7\x64\bin\bundle.bat' failed with exit code 1
|
|
windows-2022 2.0
Renaming C:\Windows\System32\libcrypto-1_1-x64.dll and C:\Windows\System32\libssl-1_1-x64.dll to avoid dll resolution conflicts on Ruby < 2.4
|
|
windows-2022 2.1
Renaming C:\Windows\System32\libcrypto-1_1-x64.dll and C:\Windows\System32\libssl-1_1-x64.dll to avoid dll resolution conflicts on Ruby < 2.4
|
|
windows-2022 2.3
Renaming C:\Windows\System32\libcrypto-1_1-x64.dll and C:\Windows\System32\libssl-1_1-x64.dll to avoid dll resolution conflicts on Ruby < 2.4
|
|
windows-2022 2.2
Renaming C:\Windows\System32\libcrypto-1_1-x64.dll and C:\Windows\System32\libssl-1_1-x64.dll to avoid dll resolution conflicts on Ruby < 2.4
|