-
Notifications
You must be signed in to change notification settings - Fork 0
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
[WOR-4059] - Upgrade to ruby 3.2.3 #2
Conversation
- Upgrade rspec gem and fix specs - Dockerfile and docker compose
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.
Looks fine to me. I'll assume that version.rb
and Gemfile.lock
will be updated to the new, non-pre-release version as part of reintegration.
Gemfile.lock
Outdated
@@ -1,33 +1,41 @@ | |||
PATH | |||
remote: . | |||
specs: | |||
signature (0.1.8) | |||
signature (0.1.9) |
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.
Weird that this wasn't set to a version that matched the lib/signature/version.rb
one already.
On that subject, I see that you appear to have pushed a pre-release version as 1.0.0...
. I think I'd probably go with 0.2.0
for this, since it doesn't seem like it actually has any compatibility-breaking changes? (Not that it matters too much, since we're the only consumers of this version of the gem.)
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.
Just one minor cleanup issue. Otherwise seems to run fine.
Gemfile.lock
Outdated
@@ -1,33 +1,41 @@ | |||
PATH | |||
remote: . | |||
specs: | |||
signature (0.1.8) | |||
signature (1.0.0) |
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.
Cleanup: Gemfile.lock didn't get updated after you changed the version number from Dylan's comment. You'll need to run bundle lock
again and push up the change.
https://wfspearson.atlassian.net/browse/WOR-4059
This PR upgrades the rspec version (latest). I didn’t see a reason to not to go to latest version but I did had to upgrade it since ruby don’t implement the method
exists?
anymore. The specs were updated to work with the newest rspec.I also added a Dockerfile and docker-compose because I had issues installing
eventmachine v1.0.7
natively (I believe this has something to do with my M1 Sonoma MacOS since it works without any issues in ruby:3.2.3-alpine3.19 docker image).I don’t think the docker is 100% necessary but this is the way I found to be able to run the tests locally.
Tests passing: