Release preparation

[h4nsu]

This PR prepares for release and deployment. See RELEASE_TODO.md for detailed release procedure

INB4: No, changing values of constants unused by the contract does not change the WASM build outcome ;)

[deuszx]

Why did you remove the toolchain file?

[h4nsu]

Because it prevented cargo contract 3.2.0 from compiling (newer rust was needed for clap)

[deuszx]

Because it prevented cargo contract 3.2.0 from compiling (newer rust was needed for clap)

What do you need clap for? Just bump the toolchain then. if we don't include it in the build it will be overwritten from the local env (or docker) and might affect the result.

[h4nsu]

cargo contract uses clap, the workflow builds and installs cargo contract

[deuszx]

cargo contract uses clap, the workflow builds and installs cargo contract

If we use the docker method I showed, you won't have that problem, as cargo contract binary is already available there.

[h4nsu]

You mean use the docker container in CI workflow?

[deuszx]

Yes, why not. It's very fast. The docker image is only 300mb and could be cached but I don't think we will re-run it many times.

[h4nsu]

I don't know how to do it straight away, and I don't think it's worth the effort of learning. The whole CI is just a cargo test followed by a check if the contract builds at all.

[deuszx]

We already do it both in common-amm and MOST. You can check it out there

[deuszx]

Can we remove the binary wrapped_azero.wasm from the repo ? At least until we provide the command how to build it deterministically.

Also, we need to bring back the rust-toolchain.toml as it might affect the final build result - ie even within the reproducible env, having different toolchains can result in different Wasm produced.

[deuszx]

Can we remove the binary wrapped_azero.wasm from the repo ? At least until we provide the command how to build it deterministically.

Also, we need to bring back the rust-toolchain.toml as it might affect the final build result - ie even within the reproducible env, having different toolchains can result in different Wasm produced.

[h4nsu]

I added the .wasm file with all other compilation artifacts as PLACEHOLDERS that will be replaced with real values after the release happens.

If we build it with the docker image why do we need rust-toolchain file? Isn't the environment fixed by what's inside the image?