Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Drop Ruby < 3.0 support #1542

Closed
AlexWayfer opened this issue Dec 25, 2023 · 1 comment
Closed

Drop Ruby < 3.0 support #1542

AlexWayfer opened this issue Dec 25, 2023 · 1 comment

Comments

@AlexWayfer
Copy link
Contributor

Basic Info

  • Faraday Version: 2.8.1
  • Ruby Version: 2.7.8

Issue description

  1. Ruby <= 2.7 is no longer supported, even with security patches.
  2. Now simple standard gem update --system or gem install bundler are broken, but I believe there no reason to report about this, because, as I've already wrote, it's no longer supported.

Steps to reproduce

  1. Install Ruby 2.7.8.
  2. Run gem update --system or gem install bundler.

Details

> gem update --system
Updating rubygems-update
Fetching rubygems-update-3.5.3.gem
ERROR:  Error installing rubygems-update:
	There are no versions of rubygems-update (= 3.5.3) compatible with your Ruby & RubyGems
	rubygems-update requires Ruby version >= 3.0.0. The current ruby version is 2.7.8.225.
ERROR:  While executing gem ... (NoMethodError)
    undefined method `version' for nil:NilClass

https://cirrus-ci.com/task/4917812326563840?logs=install#L0

> gem install bundler
ERROR:  Error installing bundler:
	The last version of bundler (>= 0) to support your Ruby & RubyGems was 2.4.22. Try installing it with `gem install bundler -v 2.4.22`
	bundler requires Ruby version >= 3.0.0. The current ruby version is 2.7.8.225.

https://cirrus-ci.com/task/6537682302533632?logs=install#L0


What do you think? Do you really still want to continue to support such old Ruby versions?

@AlexWayfer
Copy link
Contributor Author

Probably it should be a discussion. 🤔 Sorry, I'm still not familiar with this separation, you're free to move/convert.

@lostisland lostisland locked and limited conversation to collaborators Dec 27, 2023
@iMacTia iMacTia converted this issue into discussion #1543 Dec 27, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant