Skip to content

Conversation

@SkymanOne
Copy link
Contributor

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 of ink_e2e crate.

@pmikolajczyk41 pmikolajczyk41 self-requested a review December 1, 2023 08:08
@pmikolajczyk41
Copy link
Member

you probably have to add something like wasm-instrument = { version = "0.4.0", features = ["sign_ext"] } to fix compilation

@ascjones
Copy link

ascjones commented Dec 1, 2023

Here is a solution to this very annoying problem: use-ink/cargo-contract#1416.

@deuszx
Copy link
Collaborator

deuszx commented Dec 1, 2023

Don't forget to bump drink! version as well.

@pmikolajczyk41 pmikolajczyk41 merged commit e59baf9 into use-ink:main Dec 4, 2023
Comment on lines +27 to +29
contract-build = { version = "4.0.0-rc.1" }
contract-metadata = { version = "4.0.0-rc.1" }
contract-transcode = { version = "4.0.0-rc.1" }
Copy link
Collaborator

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 ?

@deuszx deuszx mentioned this pull request Feb 24, 2024
@pmikolajczyk41 pmikolajczyk41 mentioned this pull request Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants