You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RubyGems.org has a mismatching sha256 checksum for the gem and bundler is very very upset about it.
rubygems/rubygems.org#1551 and this has happened to a bunch of gems apparently. Seems the fix is to yank the mismatched gem and re-release a patch version, as seen in lostisland/faraday#679, forcing rubygems.org to get a correct hash. (Or something like that.)
This is especially fun because it appears bundler is the only one interested in the hash of the actual gem file. The gem command itself only concerns itself with the sha512 hashes of the contained data and metadata gzips. 🤷♂️
The text was updated successfully, but these errors were encountered:
RubyGems.org has a mismatching sha256 checksum for the gem and bundler is very very upset about it.
rubygems/rubygems.org#1551 and this has happened to a bunch of gems apparently. Seems the fix is to yank the mismatched gem and re-release a patch version, as seen in lostisland/faraday#679, forcing rubygems.org to get a correct hash. (Or something like that.)
This is especially fun because it appears bundler is the only one interested in the hash of the actual gem file. The
gem
command itself only concerns itself with the sha512 hashes of the contained data and metadata gzips. 🤷♂️The text was updated successfully, but these errors were encountered: