-
Notifications
You must be signed in to change notification settings - Fork 20
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
Update cargo-contract crate versions #91
Conversation
you probably have to add something like |
Here is a solution to this very annoying problem: use-ink/cargo-contract#1416. |
Don't forget to bump drink! version as well. |
contract-build = { version = "4.0.0-rc.1" } | ||
contract-metadata = { version = "4.0.0-rc.1" } | ||
contract-transcode = { version = "4.0.0-rc.1" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed that - I don't think the main release of drink!
to crates should be done against release candidates. There are other projects that depend on drink!
from crates.io and they might get silently broken now.
Judging from the diff though - there aren't that many changes. Does it mean ink5
is backwards comptible with ink4
?
As part of ink! 5.0.0-rc and cargo-contract 4.0.0-rc we need to update
drink
dependency in order to publish the updated version ofink_e2e
crate.