v0.1.0-alpha.1 Release Gate Checklist
This checklist defines the evidence required before tagging v0.1.0-alpha.1.
Current status: Not run on final merged release candidate. Historical validation records may show earlier green runs, but they are not sufficient tag evidence until the commands below are run against the current merged release-candidate commit.
Required Gates
Section titled “Required Gates”| Gate | Command to Run | Evidence Location | Current Status |
|---|---|---|---|
| Docs site tests | npm --prefix docs-site test | docs/validation/2026-04-30-alpha-docs-quality-review.md | Not run on final merged release candidate |
| Docs build | make docs-build | GitHub Actions Docs run or local build log linked from validation record | Not run on final merged release candidate |
| Docs navigation validation | uv run python testing/ci/validate-docs-navigation.py | GitHub Actions Docs run or local command output linked from validation record | Not run on final merged release candidate |
| Full CI | GitHub Actions CI workflow on the merged release-candidate commit | GitHub Actions CI run URL linked from validation record | Not run on final merged release candidate |
| Helm CI | GitHub Actions Helm CI workflow on the merged release-candidate commit | GitHub Actions Helm CI run URL linked from validation record | Not run on final merged release candidate |
| Security scans | GitHub Actions security scan jobs on the merged release-candidate commit | GitHub Actions CI and Helm CI run URLs linked from validation record | Not run on final merged release candidate |
| Unit tests | GitHub Actions CI unit matrix on Python 3.10, 3.11, and 3.12 | GitHub Actions CI run URL linked from validation record | Not run on final merged release candidate |
| Customer 360 demo deployment | make demo in the remote DevPod release-validation lane | Final Customer 360 validation record under docs/validation/ | Not run on final merged release candidate |
| Customer 360 run trigger | make demo-customer-360-run in the remote DevPod release-validation lane | Final Customer 360 validation record with dagster.run_id | Not run on final merged release candidate |
| Customer 360 validation | make demo-customer-360-validate in the remote DevPod release-validation lane | Final Customer 360 validation record with business, storage, lineage, tracing, and Dagster evidence | Not run on final merged release candidate |
| Customer 360 cleanup | make demo-stop after validation evidence is captured | Final Customer 360 validation record or operator notes | Not run on final merged release candidate |
| DevPod remote E2E | make devpod-test | test-artifacts/devpod-run-*/output.log path linked from validation record | Not run on final merged release candidate |
| #263 release posture | Confirm the GitHub issue records non-blocking alpha scope | Final validation record and issue link | Not run on final merged release candidate |
Validation Records
Section titled “Validation Records”- 2026-04-29 Alpha Customer 360 Release Validation is historical evidence only. It predates the Starlight docs migration and final alpha release-candidate validation.
- 2026-04-30 Alpha Docs Quality Review records this docs quality hardening pass and the remaining release validation required before tag.
Known Alpha Limitations
Section titled “Known Alpha Limitations”- The alpha release requires Customer 360 validation with Iceberg enabled.
- Dagster without
floe-iceberginstalled is not part of the alpha promise. - #263 remains post-alpha architecture debt only if the release-scope issue posture still classifies it as non-blocking for
v0.1.0-alpha.1. - API validation can satisfy service evidence when recorded with command output, but manual UI screenshots are not required unless the release owner adds that gate.
Tag Rule
Section titled “Tag Rule”Do not tag v0.1.0-alpha.1 until every required gate above has current evidence from the final
merged release-candidate commit and the validation record links that evidence.