Closed nevans closed 3 months ago
I'm assuming that working around this is as simple as requesting ruby/setup-ruby
install a specific version of rubygems/bundler.
BTW, I found another example of a failing build here: https://github.com/segiddins/rubygems-await/actions/runs/9517744059
😜
Just hit the same issue today while attempting to release a new version of Faraday
As @nevans mentioned above, the new version seems to have been released actually, but I didn't receive the usual email from Rubygems about the new version, so unsure if everything went well 🤔
OK so it seems like a recent refactor of Bundler's internal meant the functionality provided by @cache.dependencies
has been moved into a new @parser
object.
Should be an easy fix with a version check, I can open a PR to give it a stub. cc @segiddins
PR is ready: https://github.com/segiddins/rubygems-await/pull/46
I see an infinite (until timeout) loop of:
I can verify that the gem was successfully built and pushed: https://rubygems.org/gems/net-imap/versions/0.4.13
Ruby version: ruby 3.3.1 (2024-04-23 revision c56cd86388) [x86_64-linux] Bundler version: "Using Bundler 2 shipped with ruby-3.3.1" (I think that was 2.5.9?)
Link to failed action: https://github.com/ruby/net-imap/actions/runs/9536527233/job/26283588269