-
Notifications
You must be signed in to change notification settings - Fork 17
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
Upgrade to ruby 2.7.1 #1828
Upgrade to ruby 2.7.1 #1828
Conversation
f1868cb
to
2a1df0b
Compare
|
02f548c
to
2ad4fa6
Compare
2ad4fa6
to
1c4aa37
Compare
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.
I'd suggest the following tiny changes, based on our discussions earlier today:
- Revert the version bump in the .ruby-version and Dockerfile for now
- Ensure tests pass for 2.7.1 and update commit title to 2.7.1 from 2.7.0
- Fix spelling of 'deprecation' in commit title
7d7ef6d
to
6b70e4e
Compare
6b70e4e
to
b395bbc
Compare
9e90104
to
d89943c
Compare
Splitting the last argument into positional and keyword parameters is deprecated
Ruby 2.7 shows a warning for this obsolete method, which has actually been obsolete for over 10 years now. This alternative method encodes `/` as well, so need to substitute those back in.
It's better to have the version of Ruby stored in just one place
d89943c
to
bcd5de8
Compare
These are the changes required to upgrade to ruby 2.7
There's a script that can be run to change the ruby version across all apps, so I've made the necessary changes for 2.7.1 but left the version as 2.6.6. However, the tests don't pass under ruby 2.6.6.
Visual regression results:
https://government-frontend-pr-1828.surge.sh/gallery.html
Merged changes are automatically deployed to staging and production.
Make sure you follow the guidance for deployments before you merge.
Check your branch is being deployed in the Release app, after merging.