-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore: upgrade to rails 7.2, ruby {3.2, 3.3} and add test config #6
base: master
Are you sure you want to change the base?
Conversation
a2d3509
to
d0d178a
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.
@adi-herwana-nus some comments
Also, make sure to bump the version by changing the versioning inside lib/active_record/acts_as/version.rb
@@ -23,8 +24,19 @@ jobs: | |||
runs-on: ubuntu-latest | |||
strategy: | |||
matrix: | |||
ruby-version: ['3.0', '3.1', '3.2'] | |||
activerecord: ['6.0', '6.1', '7.0', '7.1'] | |||
ruby-version: ['3.0', '3.1', '3.2', '3.3'] |
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.
actually, since now we're already in Rails 7.0 and Ruby 3.1, we only need the testing for
- Rails 7.0, 7.1, 7.2
- Ruby 3.1, 3.2, 3.3
The inclusion of Rails 6.0, 6.1 and also Ruby 3.0 is okay, just that it's redundant for our codebase (this library is only for our internal usage anyway)
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.
Removed the rails 6 configurations, leaving behind rails 7.0, 7.1, 7.2 and Ruby 3.0, 3.1, 3.2, 3.3.
@@ -14,6 +14,7 @@ on: | |||
branches: ['master'] | |||
schedule: | |||
- cron: '0 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.
please consider carefully if you might need to remove this cron.. If you maintain this, the testing will be run once a week and last time, the test failed unexpectedly while nothing has changed.
You might want to investigate those as well
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.
Added workflow_dispatch
trigger to run actions manually to resolve intermittent failures.
d0d178a
to
6787570
Compare
- migrated pipeline from 'coveralls' to 'coveralls_reborn' - update test case for ruby 3.3 - bump version and update changelog
6787570
to
6861603
Compare
coveralls
tocoveralls_reborn
due to incompatibility with ruby 3.2+.RUBY_VERSION
variable for a specific test case broken by Ruby 3.3 message formatting change.