Repository navigation
Fix release workflow to run rake release without bundle exec - #133
Merged
Merged
Conversation
Replace the `rubygems/release-gem` action with individual steps in `push_gem.yml` to run `rake release` without `bundle exec`. When releasing ipaddr itself, `bundle exec rake release` fails because an older version of the default `ipaddr` gem is already activated, while the Gemfile requires the version being released: You have already activated ipaddr 1.2.7, but your Gemfile requires ipaddr 1.3.0. Since ipaddr is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports ipaddr as a default gem. (Gem::LoadError) The `rubygems/release-gem` action hardcodes `bundle exec rake release`, so it cannot be used to release ipaddr.
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
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.
Summary
Replace the
rubygems/release-gemaction inpush_gem.ymlwith individual steps so thatrake releaseruns withoutbundle exec.Why
The release of ipaddr 1.3.0 failed at the
rubygems/release-gemstep:https://github.com/ruby/ipaddr/actions/runs/38839750361/job/116776868213#step:6:56
rubygems/release-gemhardcodesbundle exec rake release, so it cannot be used to release ipaddr.Running
rake releasedirectly avoids the conflict between the activated default gem and the Gemfile.Changes
rubygems/release-gemv1.4.1 and runrake releaseinstead ofbundle exec rake release.https://github.com/rubygems/release-gem/blob/v1.4.1/action.yml