Skip to content

[AAASM-2959] 🔧 (release-python): Sync Cargo.lock in pin-ffi-to-tag.sh #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Chisanan232 merged 1 commit into from
Jun 15, 2026
Merged

[AAASM-2959] 🔧 (release-python): Sync Cargo.lock in pin-ffi-to-tag.sh #124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .github/scripts/pin-ffi-to-tag.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,3 +98,17 @@ PY

echo "aa-ffi git deps pinned to ${sha}:"
grep -nE '^aa-(core|proto|sdk-client)[[:space:]]*=' "$CARGO_TOML"

# Sync the sibling Cargo.lock so it agrees with the freshly-pinned rev.
# Without this the manifest points at the new core commit while the lock
# still records the old one; the wheel build only tolerates that because it
# does not run `--locked` (cargo silently re-resolves). Syncing keeps the
# lock honest and lets the build be hardened with `--locked` later. The
# maturin build mounts this same checkout, so the synced lock is what it uses.
LOCKFILE="$(dirname "$CARGO_TOML")/Cargo.lock"
if [[ -f "$LOCKFILE" ]] && command -v cargo >/dev/null 2>&1; then
echo "::notice::Syncing ${LOCKFILE} to ${sha}"
cargo update --manifest-path "$CARGO_TOML" -p aa-core -p aa-proto -p aa-sdk-client
else
echo "::warning::skipped Cargo.lock sync (cargo or ${LOCKFILE} missing); build will re-resolve"
fi