Closed kachick closed 2 years ago
It sounds a bit too much to me to drop support this early.
The failure on ruby 2.7 should be simple to fix by replacing skip
with omit
. Failures on ruby 2.6 and earlier seem like a real regression caused by https://github.com/ruby/pathname/commit/1744e33c5df93639d0229b45dfb2e6ec1395fc14. They should be easy to fix by applying the necessary part from https://github.com/ruby/ruby/commit/59c3b1c9c843fcd2d30393791fe224e5789d1677.
Finally, I think https://github.com/ruby/pathname/commit/0d1b754d3a32c2e26e5f9ed21a02b74489c0910a is a wrong motivation to stop testing versions in CI: gemifying a standard library means it can be upgraded from older rubies as long as the gem supports them, so those should still be tested until support is officially dropped.
Agreed. It caused by my laziness. It should be set >= 2.6
.
Oh, sorry I didn't know these Gemfied repositories should support which ruby versions... ๐ฎ
Hmm... @deivid-rodriguez told me so good references, thank you for the digging ๐
So I might to try to support >= 2.6
๐
(Then can we drop 2.5
? It is not yet EOL. ๐ค )
I have tried it, but hmm... sorry I can not immediately resolve some of issues ๐
First of it is https://github.com/ruby/pathname/pull/3/commits/50596427bd452293ada46b9bd9f93e59b06ab46f, I didn't know ruby accepts integer key as a keyword arguments since ruby 2.7...(Or it is my misunderstanding? ๐ )
It used in spawn
, but looks can not be used in 2.6. So just omitted..
Second issue looks CI, them I can finish running tests in my local, but CI looks fault https://github.com/ruby/pathname/pull/3/checks?check_run_id=2224125960
The error looks weird.
Error: test_split(TestPathname): TypeError: hash key 6 is not a Symbol
/home/runner/work/pathname/pathname/test/lib/core_assertions.rb:293:in `assert_separately'
/home/runner/work/pathname/pathname/test/pathname/test_pathname.rb:1071:in `test_split'
1068: def test_split
1069: assert_equal([Pathname("dirname"), Pathname("basename")], Pathname("dirname/basename").split)
1070:
=> 1071: assert_separately([], <<-'end;')
1072: require 'pathname'
1073:
1074: mod = Module.new do
===============================================================================
................O
The alerting code is nothing in this PR... So CI might using ruby bundled one? ๐ค
Ah sorry, the CI failure looks come from my changes ๐ https://github.com/ruby/pathname/pull/4 So avoid as https://github.com/ruby/pathname/pull/3/commits/dd54500bad8cdc4c438bc7eb33f048936fd1cb6c
Thanks for the update @kachick!
Then can we drop 2.5? It is not yet EOL. :thinking:
In my opinion, if the changes here are enough to support ruby 2.5, I think it's worth keeping it. I'm pushing for the same move for net-http
at https://github.com/ruby/net-http/pull/19. The gemification of these libraries is tricky since many other gems already use them, I think we can make the experience a bit smoother by being slightly conservative for the first releases at rubygems.org.
But this is up to @hsbt.
I just run into this.
My preference would be to reintroduce support for old rubies, but if this is not desired by the maintainers of this library, could we bump the required_ruby_version
in the gemspec to >= 2.7
and release a new version?
Thanks!
I created https://github.com/ruby/pathname/pull/13 to implement the alternative proposal.
@deivid-rodriguez Thanks.
@kachick I want to support only the stable versions. So, Ruby 2.6 will be EOL status at 2022/3. I will close this.
Thank you all! ๐
https://github.com/ruby/pathname/blob/a71f7d8ed28edae0db219dca7f76f6eaa74de41a/.github/workflows/test.yml#L10
This gem is testing only in Ruby 3.0+ since 0d1b754d3a32c2e26e5f9ed21a02b74489c0910a Actually, old rubies can't finish tests.
bin/setup; rake
failed as below.On ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-darwin20]
On ruby 2.3.8p459 (2018-10-18 revision 65136) [x86_64-linux]