mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-18 21:02:50 +03:00
9656084454
The 'Package artifact (npm pack policy)' base-red on release/v3.8.51 was a
false red, and 'Tarball boot-smoke' was its cascade (it is recorded as failed
whenever pack-artifact does not exit 0).
validate-pack-artifact.ts checks dist/BUILD_SHA for ancestry against
OMNIROUTE_RELEASE_REF, defaulting to origin/main. That default is correct at
publication (npm-publish.yml runs on main) but structurally impossible in
validate-release-green.mjs, which runs ON the release branch: mid-cycle its
tip is by definition not an ancestor of main, so the guard returned
off-release-line on every run.
Verified directly against the release tip d6f3150:
ref=origin/main ok=false reason=off-release-line
ref=HEAD ok=true reason=on-release-line
ci.yml already solves the same class for pull_request by pointing the ref at
the head under test; the checkable invariant here is identical - the stamp
matches the tree just validated - so the gate now runs with
OMNIROUTE_RELEASE_REF=HEAD.
The guard is not relaxed: a dist/ built from another commit still fails, and
a missing BUILD_SHA still fails. The parallel slow-gate runner also had to
forward each gate's env, which it previously dropped.
Refs #12732