mirrors/pikasTech-HWLAB
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test: guard artifact runtime readiness

Browse Source
This commit is contained in:
Code Queue Review
2026-05-23 02:31:56 +00:00
parent 0a7311c3c2
commit e3c2537091
7 changed files with 1192 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dev-deploy-apply.md
+6
View File
@@ -40,6 +40,7 @@ node --check scripts/dev-runtime-migration.mjs
node --check scripts/src/dev-runtime-migration.mjs
node scripts/deploy-desired-state-plan.mjs --check
node scripts/dev-runtime-migration.mjs --check
node scripts/artifact-runtime-readiness-guard.mjs --target-ref origin/main --check --no-report --expect-blocked
node scripts/dev-deploy-apply.mjs --dry-run --expect-blocked --write-report
node scripts/validate-dev-gate-report.mjs
```
@@ -61,6 +62,11 @@ The script refuses PROD flags, secret-read flags, heavyweight e2e flags, and
force-push flags. It also refuses to apply if the DEV artifact catalog still
contains skeleton-only unpublished images.
`deploy-desired-state-plan.mjs` is not an apply preflight substitute. Pair it
with `artifact-runtime-readiness-guard.mjs` before apply review so stale
artifact catalogs, stale desired-state, stale API runtime identity, or a stale
Cloud Web `:16666` build stay explicit blockers.
Kubeconfig selection is explicit and safe. The script uses this precedence:
1. `--kubeconfig PATH`