From 676f01869e5ed564425cf5dd1ddb5591b5b44e22 Mon Sep 17 00:00:00 2001 From: Chisanan232 Date: Sun, 14 Jun 2026 14:46:06 +0800 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20(runbook):=20Cross-reference=20a?= =?UTF-8?q?gent-assembly=20FFI=20source-pin=20auto-bump=20PR?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/release/RUNBOOK.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/docs/release/RUNBOOK.md b/docs/release/RUNBOOK.md index 1d4d743b..3181b95e 100644 --- a/docs/release/RUNBOOK.md +++ b/docs/release/RUNBOOK.md @@ -202,3 +202,28 @@ referenced agent-assembly tag does not yet have all four `aasm-*.tar.gz` assets), fix the underlying coordination problem first — usually that means running the coordinated release for `binary_source_tag` before attempting the SDK-only hotfix. + +## 5. Automatic shared-crate pin bump (from agent-assembly) + +After each `agent-assembly` release, `agent-assembly`'s `release.yml` +(`update-python-sdk-ffi-pin` job) **auto-opens a bot PR on this repo** +bumping **all three** git-SHA pins (`aa-core`, `aa-proto`, +`aa-sdk-client`) in `native/aa-ffi-python/Cargo.toml` to the just-tagged +commit. Per ADR 0002 / AAASM-2559 the three pins must share a single SHA. + +**Merging that PR does NOT republish to PyPI.** `release-python.yml` +triggers only on `repository_dispatch` (`agent-assembly-release-published`) +and `workflow_dispatch` — never on `push`. The PyPI publish already +happened at agent-assembly tag time via the coordinated +`repository_dispatch` fan-out (see section 1). + +The bump PR is **source-sync only**: it keeps the wheel's pinned crates +current so the next release — or any from-source `maturin` build — +compiles against the right revision. + +To avoid the one-cycle source lag (the wheel published at vX was built +from the *previous* pin), merge the bump PR **before** the next +agent-assembly tag is cut. + +Cross-reference: see `agent-assembly`'s `docs/release/RUNBOOK.md` +sections 3 and 8.