-
Notifications
You must be signed in to change notification settings - Fork 250
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
Compilation error on fresh Cargo.toml that depends on near-sdk-rs 4.1.1 #1119
Comments
I can see the master branch has upgrade to use near-crypto 0.17, which doesn't depend on parity-secp256k1, so I think what we need is a new release |
I see a lot of folks are hitting this issue as well. Can we make a new near-sdk-4.x release that simply bump near-crypto to 0.17? |
I hit this issue as well. This issue can also happen in GitHub CI/CD when |
@ailisp I believe it's a critical issue as it fails any builds completely and there is no workaround, isn't it? |
There is a workaround: #1126 (comment) I hope we can get 5.0 release out of the door next week |
@frol A minor update for 4.1.* with fixed dependencies should be valuable as well, as merging to 5.0 involves some breaking changes (so far) which is hard to handle quickly. |
@fadeevab It is not possible to update 4.1.1 as the dependencies are all out of date and there is no breaking-changes-free option there. Old contracts will continue working as long as they have old Cargo.lock. New contracts would better start with near-sdk-rs 5.0 going forward. |
It can be temporarily fixed until v5 is stable. Add this to
|
This is resolved with 5.0 release. |
Compiling a fresh project depends on near-sdk-rs 4.1.1 (without a Cargo.lock), I get this error:
Checking parity-secp256k1 we can see it's yanked. This possibly prevent all new projects from compiling.
The text was updated successfully, but these errors were encountered: