fix(ci): align publish workflow Ruby to 3.3.5 to fix uri activation c…#3
Merged
Merged
Conversation
…onflict
The `rubygems/release-gem@v1` action runs `bundle exec rake release`
internally, which failed on Ruby 3.2 with:
You have already activated uri 0.12.5, but your Gemfile requires uri 1.1.1
Ruby 3.2 stdlib bundles `uri 0.12.5` as a default gem. bundler 2.4.19 (also
shipped with Ruby 3.2) activates the stdlib version before checking Gemfile
requirements. Since faraday (our runtime dep) transitively resolves to
`uri >= 1.x`, bundler then errors on the version mismatch.
Ruby 3.3.5 (already what `.ruby-version` pins for local dev) ships bundler
2.5.x, which handles default-gem overlap correctly.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
…onflict
The
rubygems/release-gem@v1action runsbundle exec rake releaseinternally, which failed on Ruby 3.2 with:Ruby 3.2 stdlib bundles
uri 0.12.5as a default gem. bundler 2.4.19 (also shipped with Ruby 3.2) activates the stdlib version before checking Gemfile requirements. Since faraday (our runtime dep) transitively resolves touri >= 1.x, bundler then errors on the version mismatch.Ruby 3.3.5 (already what
.ruby-versionpins for local dev) ships bundler 2.5.x, which handles default-gem overlap correctly.