-
Notifications
You must be signed in to change notification settings - Fork 13
chore: test ruby 2.3 thru 3.4 [SC-35314] #211
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
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
madhuravius
left a comment
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.
LGTM - we MIGHT want multiple docker-compose.yml runners locally to test different versions locally but that's a huge overoptimization
what doesn't work locally? make lint test RUBY_VERSION=2.3
make lint test RUBY_VERSION=2.4
make lint test RUBY_VERSION=2.7
make lint test RUBY_VERSION=3.3
make lint test RUBY_VERSION=3.4 |
2.7 was failing due to using the older version of activesupport, which is also fixed in this pr.
also add
make test RUBY_VERSION=X.Yandmake lint RUBY_VERSION=X.Yto make it simple to repro issues locally