-
-
Notifications
You must be signed in to change notification settings - Fork 413
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
Release new version for rails 6.0.0 ? #430
Comments
Big +1, this is our only blocker for upgrading and we'd love to get it done! |
blocker for us too. Any issue with updating the gem to support 6.0.0 or it's just matter of bump it in the gemspec? |
Bumping once again! It'd be really great if we could get this done to get ourselves upgraded. |
In the same boat over here. This is the only blocker preventing us from upgrading. It's really unfortunate, as it's such a straightforward issue to resolve. Just in case you've got notifications for the repo off, do you mind releasing the next version @jnunemaker ? Edit: Apologies! Didn't see the WIP PR. |
You can follow the PR here: #429 And while we are waiting we can use the latest commit of |
New version coming soon. Hopefully today. |
0.17 is out on rubygems. |
0.17.1 is out with a fix if you are using flipper-active_record. I yanked the 0.17.0 versions of all gems because #437 basically made that version unusable for rails. |
Hello! Rails 6.0.0 has been released and I've been personally using the latest version of this gem with rc1 and rc2 in production without any issues. Could you release a new version with the changes made to
flipper-active_record.gemspec
3 months ago so we can upgrade to rails 6.0.0? 🙏 🎉The text was updated successfully, but these errors were encountered: