Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[move-cli] Update framework branch in sui move new template (MystenLa…
…bs#11614) ## Description Differentiate the branch that node operators build their software off of (e.g. `mainnet`) from the branch that Move package developers depend on the framework at (e.g. `framework/mainnet`). This is to account for the fact that when a protocol version/binary upgrade includes a framework change, there is a period of time between when the tracking branch for node operators (e.g. `mainnet`) is updated and when the network performs the protocol upgrade where an attempt to publish a package that depends on a system package will fail because of dependency source validation. This PR also introduces some other minor changes to the new package template: - Remove an extraneous space in the `addresses` output. - Don't include the address for `sui` because it will be inherited from the `Sui` dependency automatically. ## Test Plan Test output from `sui move new` ``` crates/sui$ cargo run -- --path /tmp/example example crates/sui$ cat /tmp/example/Move.toml [package] name = "example" version = "0.0.1" [dependencies] Sui = { git = "https://github.com/MystenLabs/sui.git", subdir = "crates/sui-framework/packages/sui-framework", rev = "framework/testnet" } [addresses] example = "0x0" ``` Test script that checks compatibility against localnet: ``` crates/sui$ cargo build sui$ export SUI=$(git rev-parse --show-toplevel)/target/debug/sui sui$ $SUI genesis -f && $SUI start # In a new terminal session sui$ export SUI=$(git rev-parse --show-toplevel)/target/debug/sui sui$ $SUI client switch --env localnet sui$ ./scripts/check-framework-compat.sh ``` --- If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process. ### Type of Change (Check all that apply) - [x] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes The revision that the framework used by `$NETWORK` is found it is now `framework/$NETWORK` and not just `$NETWORK`.
- Loading branch information