-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
0.3.2 contains a breaking change #6
Labels
Comments
Ah, crap. I forgot about Line 68 in e54e093
Let me see if I can do this quickly. It may not happen until after 6pm PT. |
Ok thanks! If possible, mind doing a quick yank for us? |
Ah I see it's in there now, thanks! |
It's been yanked. I'll release a 0.3.3 shortly. |
This was referenced Dec 20, 2018
0.3.3 has been released, without the API change. |
Thanks so much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're seeing breakage on Rust's CI for a breaking change in the 0.3.2 release:
It looks like a reference wasn't previously needed but now it is? Would it be possible to yank 0.3.2 and publish 0.3.3 with a fix?
The text was updated successfully, but these errors were encountered: