Correr el job de release en Ruby 3.4 - #34
Merged
Merged
Conversation
rubygems/release-gem enables attestations by default, which preloads a patch via RUBYOPT that requires rubygems/commands/push_command before Bundler.setup runs. That activates Ruby's default securerandom, and Bundler then aborts because Gemfile.lock pins 0.4.1 (activesupport 8.0, pulled in through money-rails, requires securerandom >= 0.3). Ruby 3.2 ships securerandom 0.2.2 and 3.3 ships 0.3.1, so both conflict; 3.4 ships 0.4.1 and matches the lockfile. The release job only builds and pushes the gem, so it does not need to run on the minimum supported Ruby version. CI still covers 3.2, 3.3 and 3.4.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contexto
El workflow de release falla al publicar la gem:
bundle exec rake releaseexplota con un conflicto de activación desecurerandom.¿Qué hay de nuevo?
ruby-versionpasa de3.2.2a3.4enrelease.ymlTests
Consideraciones
rubygems/release-gemprecarga un patch víaRUBYOPTque activa elsecurerandomdefault de Ruby antes deBundler.setup. Ruby 3.2 trae 0.2.2 y 3.3 trae 0.3.1; el lockfile pide 0.4.1, que es el que trae 3.4.ci.ymlsigue cubriendo 3.2, 3.3 y 3.4.Created with Claude Code
/fast-trackcommand