-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Rails 5.2 #305
Comments
For the record, #264 is also a blocker for Rails 5.2 compatibility. |
#264 is now closed :) |
Are there other blocking issues that are known? What's the release pattern, do you typically fork a branch with the new environment and add it to the CI for testing? |
I've been testing the current master for a few days and for us, everything works fine. |
@grk and @n-rodriguez could you guys check out #308 and #309 ? I'll merge that if the three of you all agree that the PR is correct. (I'm also looking for more committers for ClosureTree!) |
Builds on 5.2 have been green for a while. Closing. Thanks for everyone's help. Time for v7.0.0! |
Any news on the release of 7.0.0? |
217162c you fixed #296.
Rails 5.2 is not officially released. Could you also bump/release your gem to include this fix?
The text was updated successfully, but these errors were encountered: