fix(release): the workspace crates' exact pins move with the version
ci / gate (push) Successful in 12m17s
release / linux (push) Successful in 14m25s
release / package (44) (push) Successful in 40s
release / publish (44) (push) Successful in 12s

91ec5fb bumped the workspace to 0.2.0 but left wallet-entities,
wallet-core and wallet-data pinned to each other at =0.1.0, so Cargo.lock
no longer resolved. The pins are now =0.2.0, the lockfile follows, and
script/stamp-version.sh rewrites the pins from the workspace version so
the next bump cannot leave them behind. Gate run with --locked.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014ftBXYuba8ARhQeF74oUgW
This commit is contained in:
2026-09-16 19:24:11 +03:00
co-authored by Claude Opus 5
parent 91ec5fbadb
commit dff158e457
3 changed files with 10 additions and 7 deletions
+3
View File
@@ -17,6 +17,9 @@ if [ "${1:-}" != "" ]; then
exit 1
fi
fi
# The workspace's own crates pin each other exactly; keep the pins on the
# workspace version, or a bump leaves Cargo.lock unresolvable.
sed -i -E "s/^(wallet-[a-z]+ = \{ path = \"crates\/wallet-[a-z]+\", version = \")=[^\"]+(\" \})/\1=${version}\2/" "${here}/Cargo.toml"
python3 - "${version}" "${here}/crates/wallet-app/tauri.conf.json" "${here}/ui/package.json" <<'PY'
import json, sys
version, *files = sys.argv[1:]