-
Notifications
You must be signed in to change notification settings - Fork 209
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
primeorder 0.13.4 update breaks p384 0.13.0 builds #984
Comments
What's the build failure? |
From our CI builds of https://github.com/bevyengine/bevy/actions/runs/6884781565/job/18727900621#step:5:486 |
Aah, thanks |
tarcieri
added a commit
that referenced
this issue
Nov 16, 2023
...as an associated type of `PrimeCurveParams`. This was an accidental breaking change which broke the build for released crates: #984
tarcieri
added a commit
that referenced
this issue
Nov 16, 2023
...as an associated type of `PrimeCurveParams`. This was an accidental breaking change which broke the build for released crates: #984
I've released v0.13.6 as a replacement which should hopefully address this problem |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
primeorder
0.13.4 update brokep384
v0.13.0 builds. There were changes top384
on master branch to get it to build withprimeorder
0.13.4.primeorder
0.13.4 should probably be yanked to avoid breakage. The dirtier option is doing a0.13.1
patch release forp384
containing the fix, but this wouldn't help other consumers ofprimeorder
.This breaks bevy builds so fixing this is a high priority for us.
@tarcieri
The text was updated successfully, but these errors were encountered: