Skip to content
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

Merged
merged 5 commits into from
Feb 28, 2024

Conversation

weslleyalmd
Copy link

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.

Screenshot 2024-02-14 at 17 47 12

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:
Screenshot 2024-02-14 at 14 54 43

- Upgrade rspec gem and fix specs
- Dockerfile and docker compose
@weslleyalmd weslleyalmd self-assigned this Feb 14, 2024
Copy link

@dleeman dleeman left a 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)
Copy link

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.)

Copy link

@AMathews AMathews left a 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)

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.

@weslleyalmd weslleyalmd merged commit 7ea12e9 into master Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants