Validate candidate migration baseline during release

2026-08-04 15:01:50 +02:00
parent 077735bc24
commit 8e890b37ed
3 changed files with 17 additions and 4 deletions
@@ -59,9 +59,11 @@ 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.

-The same release entry point records the reviewed current Alembic heads under
-the target release version and reruns the strict migration audit before it
-changes package versions, commits, or tags. A failed baseline check therefore
+The same release entry point first validates the migration graph, then records
+the reviewed current Alembic heads under the target release version and reruns
+the strict migration audit before it changes package versions, commits, or
+tags. The default preflight intentionally does not require those heads to exist
+in the previous release baseline. A failed candidate-baseline check therefore
 cannot produce a protected package release.

 It builds one wheel and, where applicable, one npm tarball. The workflow records