-
Notifications
You must be signed in to change notification settings - Fork 317
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
chore: lock versions to the correct minor, and update #1613
chore: lock versions to the correct minor, and update #1613
Conversation
1. Update minimum versions for in-workspace crates. 2. Use the tilde constraint to ensure that we don't update to the next minor version. The next minor version is going to revert the change.
e5dc008
to
4a9a4c0
Compare
is CI sad because it was opened from a fork? |
No that's not the issue. I think I know how to fix that. |
@arajasek I was wrong, it was the issue. Though, this PR should be green soon. |
@vmx CI still sad :( |
Looks like something timed out. |
02e7ad5
to
90c56b0
Compare
It's failing to fetch parameters. I'm seeing if I can get that working. |
|
For the record: this exact change passed all tests, when the CI was fixed. It's shown at #1614. |
* feat: extend proofs API such that aggregation can use snarkpack versions * feat: extend aggregation tests to ensure version incompatibility * feat: update bellperson and neptune to latest * feat: update CI nightly * feat: update dependencies * feat: lock versions so only patch releases are allowed Based on #1613 * feat: update merkletree to latest release * docs: update changelog for release * docs: update changelog for release * feat: update neptune to the latest release
Otherwise, the next minor release (which will re-release the changes on master) will break anything depending on this release.
NOTE: we should also go ahead and release those minor releases. This is kind of hard to test otherwise.