Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Ruby 3.3 for gh_pages build #109

Merged
merged 1 commit into from
Jul 21, 2024

Conversation

jeremyevans
Copy link
Contributor

Hopefully this will fix the following error:

You have already activated uri 0.12.1, but your Gemfile requires uri 0.13.0. Since uri is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports uri as a default gem.

https://github.com/ruby/uri/actions/runs/10029934700/job/27718711665#step:5:38

Hopefully this will fix the following error:

You have already activated uri 0.12.1, but your Gemfile requires uri
0.13.0. Since uri is a default gem, you can either remove your
dependency on it or try updating to a newer version of bundler that
supports uri as a default gem.
Copy link
Contributor

@olleolleolle olleolleolle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This got us to green, thank you!

@jeremyevans jeremyevans merged commit cd1e539 into ruby:master Jul 21, 2024
24 checks passed
@jeremyevans
Copy link
Contributor Author

Unfortunately, this doesn't seem to have helped: https://github.com/ruby/uri/actions/runs/10030217373/job/27719279537

Maybe we need to explicitly update the bundler version?

@olleolleolle
Copy link
Contributor

@jeremyevans What if you used '3.3.4' instead of the short-hand '3.3' when telling setup-ruby the version?

This was from the erroring build's Setup Ruby step:

Print Ruby version
  /opt/hostedtoolcache/Ruby/3.3.0-preview1/x64/bin/ruby --version
  ruby 3.3.0preview1 (2023-05-12 master a1b01e7701) [x86_64-linux]
  Took   0.02 seconds

@jeremyevans
Copy link
Contributor Author

We could do that, but we really shouldn't have to. Something is broken in the tooling if 3.3 results in 3.3.0preview1 and not the latest 3.3 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants