Gate PyPI publish on draft release

Author: code5717

.github/workflows/release.yml

@@ -132,7 +132,9 @@ jobs:
 
   publish-pypi:
     runs-on: ubuntu-latest
-    needs: build-release
+    needs:
+      - build-release
+      - create-github-release
     if: startsWith(github.ref, 'refs/tags/v')
     environment:
       name: pypi

CHANGELOG.md

@@ -17,6 +17,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Release workflow permissions are split so the gate/artifact build job runs
   with read-only repository contents access; only the tag-only draft release job
   receives `contents: write`.
+- Tag-based PyPI publishing now waits for the draft GitHub release job to
+  succeed before requesting the protected `pypi` environment.
 
 ## [0.3.0] - 2026-05-07
 

RELEASE.md

@@ -107,11 +107,12 @@ The workflow keeps release permissions split: the gate/artifact build job uses
 read-only repository contents access, and only the tag-only draft release job
 uses `contents: write`.
 
-The same tag workflow publishes the Python package distributions to PyPI through
-Trusted Publishing/OIDC. The GitHub `pypi` environment exists and requires
-review by `code5717`. As of the latest release-readiness audit, `a7-py` is not
-yet a public PyPI project. Before the first real publish, create or preconfigure
-the PyPI project trusted publisher with:
+After the draft GitHub release job succeeds, the same tag workflow publishes
+the Python package distributions to PyPI through Trusted Publishing/OIDC. The
+GitHub `pypi` environment exists and requires review by `code5717`. As of the
+latest release-readiness audit, `a7-py` is not yet a public PyPI project. Before
+the first real publish, create or preconfigure the PyPI project trusted
+publisher with:
 
 - owner: `code5717`
 - repository: `a7-py`

RELEASE_READINESS_REVIEW.md

@@ -68,7 +68,7 @@ not factually provable from local tests alone.
   read-only repository contents access; only the tag-only draft release job gets
   `contents: write`.
 - Release tags now publish package distributions to PyPI through Trusted
-  Publishing/OIDC after the release gate passes.
+  Publishing/OIDC only after the release gate and draft GitHub release job pass.
 - C backend `for-in` lowering now caches iterable expressions before loop
   length and element access.
 - String literal tokenization now rejects unknown escapes and malformed `\xHH`

TODO.md

@@ -250,7 +250,7 @@ These are entire subsystems. Each needs a design decision before implementation
 
 - [x] Add PyPI or package-registry publishing.
   Files: `.github/workflows/`
-  Notes: release tags now publish built distributions to PyPI through Trusted Publishing/OIDC. The GitHub `pypi` environment exists and requires maintainer review; `a7-py` is not yet a public PyPI project, so create or configure the PyPI trusted publisher for repository `code5717/a7-py`, workflow `release.yml`, and environment `pypi` before the first real publish.
+  Notes: release tags now publish built distributions to PyPI through Trusted Publishing/OIDC after the draft GitHub release job succeeds. The GitHub `pypi` environment exists and requires maintainer review; `a7-py` is not yet a public PyPI project, so create or configure the PyPI trusted publisher for repository `code5717/a7-py`, workflow `release.yml`, and environment `pypi` before the first real publish.
 
 - [ ] Design and implement `fall` lowering.
   Files: `src/passes/semantic_validator.py`, `src/backends/zig.py`, `src/backends/c.py`, `docs/SPEC.md`