Support in-support Ruby versions only?

[olleolleolle]

The tool landscape changes, and Ruby versions with it.

2.5 is the oldest Ruby in support. Ruby support schedule: https://www.ruby-lang.org/en/downloads/branches/

Perhaps we could cut down on the maintenance burden and support only 2.5+?

[olleolleolle]

Right, so 3.0 dropped today, and we can't run the same Gemfile with it and the older things. Wrong!

Ruby 2.5: EOL date: 2021-03-31

[ku1ik]

Oh, interesting. What's the oldest 2.x version we could have with the same Gemfile supporting 3.0?

[olleolleolle]

@sickill Haha, I was just out of date, in my development checkout. Haha.

@sickill Here's an example where we'd need to wiggle around to support 3.x - using a separate Gemfile _could_ perhaps make it possible. Perhaps only time would make it possible.

➜  rainbow git:(master) ruby -v
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin20]
➜  rainbow git:(master) bundle
Fetching gem metadata from https://rubygems.org/.......
listen-3.2.1 requires ruby version >= 2.2.7, ~> 2.2, which is incompatible with
the current version, ruby 3.0.0p0
➜  rainbow git:(master)

Aha, update: https://github.com/guard/listen/releases Supports 3.

[olleolleolle]

https://endoflife.date/ruby lists the published dates in a neat little table.

I kind of want to get a release out with the old code, what's in trunk right now, and then have a clean slate to think of what we can do.

[olleolleolle]

OK, since Ruby 2.3 on AppVeyor does this: I want to cut it from the list of supported Ruby versions.

bundle install --jobs 3 --retry 3
Fetching source index from https://rubygems.org/
Retrying fetcher due to error (2/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
Retrying fetcher due to error (3/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
Retrying fetcher due to error (4/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most
likely your system doesn't have the CA certificates needed for verification. For
information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect
without using SSL, edit your Gemfile sources and change 'https' to 'http'.

[olleolleolle]

Update: I removed support for 2.3 today.