iotaledger / iota / 32205096332

69%

Build Type

push

github

Committed by web-flow

Commit Message

refactor(iota): migrate CLI publish/upgrade commands to the gRPC transaction builder (#12659)

# Description of change

Third slice of the CLI migration to the gRPC-driven SDK
`TransactionBuilder` (one command family per PR): `publish` and
`upgrade`.

- `publish` builds a `Publish` command from `MovePackageData` and
transfers the resulting `UpgradeCap` to the sender — the same PTB the
JSON-RPC `publish_tx_kind` produced.
- `upgrade` has no high-level SDK helper, so it follows the
`publish_upgrade` example in `iota-rust-sdk`:
`0x2::package::authorize_upgrade` → `Upgrade` command →
`0x2::package::commit_upgrade`. The upgrade cap is fetched over gRPC and
passed as an owned or shared-mutable input depending on its owner, with
the same rejections (immutable / object-owned cap) as before. The digest
argument BCS-serializes to the same bytes as the old `Vec<u8>`, so the
built transaction is unchanged.
- Gas payment references come from `grpc_input_refs`; gas estimation,
dry run, serialization, signing, execution and `Move.lock` updates stay
on their existing paths, so gas behaviour and CLI output are unchanged.
- JSON-RPC read paths (protocol config for compilation, upgrade policy
lookup, `--verify-compatibility`) are left as-is per the issue's
constraints.

Test-side change: `test_tree_shaking_package_deps_on_pkg_upgrade` chains
seven CLI commands in one test future and already ran within tens of
kilobytes of the test thread's 8 MiB stack on `develop` (#12341 hit the
same limit with `test_move_authenticator`); the slightly larger command
future tipped it over. The shared `publish_package` / `upgrade_package`
test helpers now `Box::pin` the command future, moving that storage to
the heap.

Still on the JSON-RPC client, by design: JSON-arg `move_call` and the
PTB command. Split/merge is in flight in #12595.

## Links to any relevant issues

Part of #12099 (task: publish / upgrade, low-level upgrade fns per the
`iota-rust-sdk` example).

## How the change has ... (continued)

Coverage Stats

21 of 21 new or added lines in 1 file covered. (100.0%)

698 existing lines in 41 files now uncovered.

170017 of 243827 relevant lines covered (69.73%)

462508.84 hits per line