Sui Fixes Cargo.lock to Restore CI Builds
Sui fixed a non-canonical tokio-util entry in Cargo.lock, introduced in commit #28447. Cargo rewrote the lockfile during unlocked builds, causing scripts/changed-files.sh to fail in CI, including the test-tidehunter workflow. The fix ensures `cargo metadata --format-version 1` leaves Cargo.lock unchanged. No user-facing protocol or product changes were listed.
Neutral
This is a repository and build-infrastructure fix for Sui, not a protocol upgrade, token-economic change, security incident, or adoption announcement. It addresses a non-canonical Cargo.lock entry that caused CI scripts to fail when Cargo rewrote the lockfile, and verifies the correction with cargo metadata. The change could improve development and testing reliability, but the article provides no evidence of an immediate effect on SUI demand, network usage, liquidity, or market stability. Similar build-pipeline fixes generally have limited trading impact unless they reveal a broader outage or delay a major release. Short-term SUI price action is therefore more likely to follow wider market conditions and other project news; the longer-term effect is a modest improvement in engineering reliability rather than a clear bullish or bearish catalyst.