Publish release tags in dependency order

2026-08-04 14:54:54 +02:00
parent bad0ea37a7
commit d9522d3cc4
3 changed files with 18 additions and 1 deletions
@@ -54,6 +54,11 @@ skips complete registry pairs and does not duplicate an active workflow. Use
 `--repository govoplan-core` for a bounded dispatch or `--verify-existing` to
 rebuild and hash-verify versions already present in both registries.

+For coordinated lockstep tags, `push-release-tag.sh` pushes module tags first,
+Core next, and the meta tag last. This is a dependency guarantee for a
+single-capacity Actions runner: the developer package cannot run before its
+exact Core and module versions have entered the queue.
+
 It builds one wheel and, where applicable, one npm tarball. The workflow records
 the source tag, source commit, filename, size, and SHA-256 in
 `package-artifacts.json` before publishing. Gitea rejects a second upload of the