-
Notifications
You must be signed in to change notification settings - Fork 204
Relax version requirement for rubyzip #491
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
Conversation
Co-authored-by: Olle Jonsson <olle.jonsson@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for contributing this change!
The test failures on 9.2.0.0 seem perhaps to be about that, on 9.2 (whereas 9.1 does not have that).
|
The test failures ought to be addressed. Perhaps the test can be relaxed, perhaps only modified.
I'll check the test failures. |
ebc9b28
to
95026c5
Compare
CI failed with:
I tried to trigger a rebuild with a |
Someone had an issue a bit like this, here: rubygems/rubygems#4150 @headius Are we committed to keeping 9.0.5.0 in the matrix still? |
@olleolleolle @headius I removed 9.0.5.0 from .travis.yml and now the tests are green. |
@ioanatia https://github.com/jruby/warbler#warbler--- the README has a promise of "9.0.0.0 and up", which I believe to be not the case anymore if we fail to run our suite on that range. Could we say, @headius, that we no longer support the < 9.1? |
@ioanatia Awesome that you edited the CI, this was new information, good! |
Thanks, the README is updated. |
@ioanatia I think latest 9.1 is sufficient for the CI. |
AFAICS jruby 9.0 is supposed to be compatible with Ruby 2.2, but support for Ruby 2.2 has ended in June 2018. |
Technically jruby 9.1 is Ruby 2.3 compatible and support for Ruby 2.3 has also ended. In addition to that, bundler 2 does not really work on jruby 9.1 due to some issues in jruby fixed in the 9.2 series (see ruby/setup-ruby#108). So maybe it's ok to drop support for jruby 9.1 too in the next version. |
Also I just installed
It seems official that jruby 9.1 is out of support, so I think it's ok to move on. |
We have not supported 9.1 for a long time now. 9.2+ seems reasonable to me unless someone shows up with a convincing story why we should continue to support it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks all, for chiming in! Merging now!
@ioanatia Thanks for the strong momentum and follow-through! |
Nice! Thanks for merging this @olleolleolle - any chance to have a new release of this gem soon? |
@ioanatia That's a little longer process, but with @deivid-rodriguez working on a GitHub Actions CI change, and we are at a green build, so if you want to support the process, please investigate what information we have about performing releases. I am new to that process, and am documenting my steps in a coordination Issue linked here. |
I found that this PR might've introduced an issue. Before, the With this PR it's failing to even start with the error: "Error installing /home/travis/.m2/repository/rubygems/rubyzip/2.3.0/rubyzip-2.3.0.gem: rubyzip requires Ruby version >= 2.4.". The "solution" seems to (again) to drop support for jruby 9.1 as well, so I'm going to propose that as a separate PR. And that surfaces yet another issue because the |
closes #490
I haven't actually test that it works with the latest version of rubyzip, but looking at the usage of the gem it looks like it should work.
Not sure whether the CI job will actually install the latest version of the gem or not.