-
Notifications
You must be signed in to change notification settings - Fork 495
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 2.5 support #2674
Drop Ruby 2.5 support #2674
Conversation
Ruby 2.5 hit end-of-life on 2021-04-05, nearly three years ago. Additionally one of Facter's dependencies, Thor, dropped Ruby 2.5 support with Thor 1.3.0 in October 2023. This commit sets Facter's minimum Ruby version to 2.6 and updates tests and Rubocop configuration accordingly.
This commit addresses all offenses triggered by the Rubocop Style/SlicingWithRange cop.
In Ruby 2.6 and greater, passing trim_mode as the third argument of ERB.new is deprecated. This commit updates all instances of ERB.new to instead use trim_mode as a keyword argument.
I think this broke puppetserver 7:
I also see it in our Ubuntu 20.04 test in the same place. https://github.com/theforeman/puppet-puppet/actions/runs/8174732159/job/22350223689?pr=908 |
@ekohl are you running puppetserver in a container? I don't see this issue using puppetserver 7 packages on Ubuntu 20.04. As can be seen below, puppetserver's jruby maintains compatibility with Ruby 2.6.8, which supports
|
It is indeed a container, because it makes CI in GitHub Actions easier |
You're installing latest puppet-agent:
But installing a two+ year old puppetserver 7.6.0. That version vendors an older JRuby 9.2, hence the error:
While we always aim to maintain compatibility within 7.x, the combination of latest agent and ancient puppetserver on the same host seems like a recipe for disaster. |
Hmm, interesting. We historically had that test to verify upgrades. Maybe we should raise the base version a bit |
This PR: