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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring CHANGELOG up to date #1442
Conversation
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.
A few suggestions, but this looks good to me. Thanks for doing this!
CHANGELOG.md
Outdated
### Backward-incompatible changes | ||
|
||
* Drop support for Rails 4.2, 5.0 and 5.1 as well as Ruby 2.4 and 2.5 | ||
they've been end-of-lifed. The gem now supports Ruby 2.6+ and Rails 5.2+.([#1412], [#1415], [#1422], [#1428],[#1429]) |
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.
Should you have a space after the period?
CHANGELOG.md
Outdated
### Features | ||
|
||
* Add support for Rails 6.1. No new Rails 6.1 features are supported, but only | ||
existing features that broke with the upgrade.([#1418]) |
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.
Should you have a space after the period?
CHANGELOG.md
Outdated
|
||
### Bug fixes | ||
|
||
* Replace in?, method from ActiveSupport, with include? to prevent exception "undefined method `in?`" on non-Rails app. ([#1405]) |
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.
Maybe place backticks around in?
and include?
here?
Oops, my bad. Done! |
馃帀