-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add support for activerecord 7.2, ruby 3.3 #35
Conversation
23cd800
to
cac6c52
Compare
cac6c52
to
52890c4
Compare
@@ -17,7 +19,7 @@ | |||
Thread.new do | |||
listener_loop(**listener_options) | |||
ensure | |||
base_class.clear_active_connections! |
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.
NOTE: delegation to the connection handler was deprecated in activerecord 7.1 and removed in activerecord 7.2.
- activerecord: '7.2' | ||
ruby: '3.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.
NOTE: activerecord 7.2 requires ruby 3.1 or greater. I added this exclusion so that we can continue to support ruby 3.0 for the time being.
@@ -1,5 +1,7 @@ | |||
# frozen_string_literal: true | |||
|
|||
require "ostruct" |
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.
We must have had a dependency which was loading this as tests were failing because OpenStruct was not loaded. I haven't tracked this down because our old build logs appear to have passed the retention period and I don't think that it's worth the effort to try to reproduce successful builds without this import.
What did we change?
Why are we doing this?
Resolves #34 so that people who are using rails 7.2 can also use this gem.
NOTES
Ruby 3.0 has been EOL for almost 5 months. I figure that a breaking change for dropping this probably warrants a separate release. Rails 6.1 is EOL in 2 weeks, so it probably makes sense to drop support for that simultaneously.
How was it tested?