-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Cut a release #972
Comments
I'll pull down the latest and test with an actual client, then push out a beta release by the end of this week. |
Good plan! |
I'm testing master as well with several projects that uses it (except Omniauth that we don't use it), for now I only found an issue #975 |
Testing master I found failing some tests in a project because I don't have the new field |
@MaicolBen it probably should check if recoverable is enabled, that's a good point. Can you find a precedent in Devise or our codebase for how to check for a module being enabled? |
Yeah, it's possible, I made a PR #995 |
While we're waiting for a release to be cut (which would be really great), is there any way to use what's in master on github in a project? Pointing to here in the gemfile still makes it use 0.1.42 code |
@Blitzkev You can doing @lynndylanhurley Any ETA in testing and publishing the release? If we are following semver, this should be 0.2.0 because we have some new features merged in master |
@Blitzkev The following is working for me:
|
Thanks for your patience all and @ethagnawl thanks for the workaround! |
Just pushed In the meantime please pull down the beta and test. Thanks!! |
Thanks @lynndylanhurley! can you take a look at #995, because it will break for the projects that update the gem. I would like #989 merged, but that's only for our projects. |
Would appreciate this merged also: |
@lynndylanhurley |
@h4b00 have you tested v0.1.43.beta1 and has it been working well for you? The more people test the beta branch, the faster we cut a release :). |
It was done, it's v0.1.43 ! |
We've merged a bunch of changes so sometime soon we should cut a new release.
The text was updated successfully, but these errors were encountered: