Closed mscrivo closed 10 months ago
Apparently so! This was noted in the comments of the prior issue: https://github.com/googleapis/google-auth-library-ruby/issues/462#issuecomment-1852317648
what a mess!
We yanked 1.9.0 from Rubygems due to #462, and we will be pushing out 1.9.1 momentarily with a fix. When a version is yanked, Rubygems is still supposed to allow installation of the yanked version if it's requested specifically (e.g. if it's in your Gemfile.lock) but won't allow new bundle resolutions to include it. So it's not supposed to break an existing build. Are you observing something different?
Yep, we started seeing this failure in our CI logs:
[2023-12-12T18:55:20Z] Your bundle is locked to googleauth (1.9.0) from rubygems repository
[2023-12-12T18:55:20Z] https://rubygems.org/ or installed locally, but that version can no longer be
[2023-12-12T18:55:20Z] found in that source. That means the author of googleauth (1.9.0) has removed
[2023-12-12T18:55:20Z] it. You'll need to update your bundle to a version other than googleauth (1.9.0)
[2023-12-12T18:55:20Z] that hasn't been removed in order to install.
[2023-12-12T18:55:21Z] 🚨 Error: The command exited with status 7
Ouch, you're right. My information about yank's behavior was not correct. (I could have sworn that in the past it was as I described, but it certainly isn't now.) Sorry about that. That was a great way to make a bad situation worse. In any case, version 1.9.1 is now out, so you should be able to update your bundle.
Seems like 1.9.0 no longer shows up here: https://rubygems.org/gems/googleauth .. our builds started failing this morning. Didn't see any other issues calling it out.