You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The whole fleet pins hydra-gates-ref: v1.0.1, which predates #147/#148/#149 — 16 dead gates are still live in CI everywhere #159
d9645e3 gate-53 ignored the diff scope; gate-22 printed FAIL — 0; gate-33 had never run (#139)
v1.1.0
❌
549ad1a16 gates reported PASS when their helper never ran (#147)
—
❌
0d3e589 produce tests/axe/report.json so gate-33 can actually run (#148)
—
❌
fc70ea6 gate-7 follows delegation; gates 6/7 stop passing on an empty scope (#149)
—
❌
So every in-CI Hydra Gates run on the fleet today is executing a script in which 16 gates report PASS when their helper never ran, and in which gates 6 and 7 report PASS on an empty scope. That is the dead-gate shape those PRs were written to close, still live everywhere.
$ for r in …; do gh api repos/ConductionNL/$r/contents/.github/workflows/code-quality.yml?ref=development \
-q .content | base64 -d | grep hydra-gates-ref; done
hydra-gates-ref: v1.0.1 # ×22, no exceptions
Decide whether the pin should be a moving minor (v1) rather than an exact patch. A patch pin means every gate fix needs a 22-repo bump PR wave, which is exactly why the fleet is 4 fixes behind after two days.
Related: the full-tree numbers I am reporting elsewhere use main, so they are not comparable to what CI prints today — worth stating explicitly wherever both appear.
Rolled. And the answer to question 2 is now forced by evidence rather than preference.
Status:v1.3.0 PRs open on 17 repos + hrmq enabled for the first time; doriath already merged; openbuild/portaliq/procest/scholiq have their own author's PRs, which I commented on rather than duplicating. Table at the bottom.
The pin was not just stale — since 13:52Z today it was RED, fleet-wide
f7eaf2a (#164) flipped hydra-gates-require-full-coverage to default true in quality.yml. That flag requires a gate to declare itself not-applicable. The vocabulary to declare ships in the pinned package:
pin
_skip calls
v1.0.1
0
v1.2.0
0
v1.3.0
36
A pin with zero _skip calls cannot say "not applicable", so gates 4/24/33 became DID NOT RUN and failed the job everywhere at once. Reproduced byte-for-byte against a real blocked PR (nldesign#220, PHPMD-only):
v1.0.1 exit 98 COVERAGE: 59 of 61 GATES THAT DID NOT RUN: 24 33
v1.3.0 exit 0 COVERAGE: 59 of 63 NOT APPLICABLE: 6 7 24 33
Confirmed in real CI on the same repo/branch, both runs after 13:52Z: app-versions 31012647428 at v1.2.0failure → 31013564400 at v1.3.0success. This is what was blocking ~14 PHPMD PRs.
Question 2: the pin must move WITH quality.yml, or not at all
Three separate desyncs in one day, all the same shape — the shared workflow is @main while the package is pinned:
(3) is the decisive one. A workflow that executes a path inside the pinned package has made the two a single unit. Pinning one and floating the other is not a conservative choice — it is an unversioned interface, and it has now failed three times in a day.
Recommendation, in preference order:
Pin both together. Consumers reference quality.yml@vX.Y.Zandhydra-gates-ref: vX.Y.Z from the same tag. One bump wave moves both; a desync becomes impossible by construction.
Failing that, float both (@main + hydra-gates-ref: main). Loses reproducibility but at least the halves always match.
What we have now — pin one, float the other — should not survive this issue.
A moving v1 minor tag does not fix this. It reduces the bump waves but leaves the workflow and package on independent clocks, which is the actual defect.
I deliberately rolled v1.3.0, not v1.4.0, for fleet uniformity with the repo that already landed, and because v1.3.0 is what demonstrably fixes today's red. v1.4.0 is a strict superset and should be a separate, measured follow-up — gh_slugify reduces gate-46 findings (openconnector: 42 with it vs 109 without), so it makes repos greener, but that is a verdict change across 22 repos and deserves its own measurement rather than riding along on an urgent fix.
One correction to my own earlier reporting in this thread
My first fallout table showed gate-22 manifest-validation newly failing in 8 repos. That was my harness, not the repos — ajv was absent locally, so the validator ran degraded and correctly refused to report a pass. CI installs ajv. With it installed, gate-22 passes in all of them, and the corrected delta is the opposite of what I first had: 12 repos lose a gate-22 failure and 5 lose gate-7. Flagging it because it is the same class of error this issue is about — a measurement artifact that reads exactly like a finding.
Activity
ci(quality): correct the target ref to v1.3.0 — v1.2.0 is RED under t…
rubenvdlinde commentedon Aug 5, 2026
Rolled. And the answer to question 2 is now forced by evidence rather than preference.
Status:
v1.3.0PRs open on 17 repos +hrmqenabled for the first time;doriathalready merged;openbuild/portaliq/procest/scholiqhave their own author's PRs, which I commented on rather than duplicating. Table at the bottom.The pin was not just stale — since 13:52Z today it was RED, fleet-wide
f7eaf2a(#164) flippedhydra-gates-require-full-coverageto defaulttrueinquality.yml. That flag requires a gate to declare itself not-applicable. The vocabulary to declare ships in the pinned package:_skipcallsv1.0.1v1.2.0v1.3.0A pin with zero
_skipcalls cannot say "not applicable", so gates 4/24/33 becameDID NOT RUNand failed the job everywhere at once. Reproduced byte-for-byte against a real blocked PR (nldesign#220, PHPMD-only):Confirmed in real CI on the same repo/branch, both runs after 13:52Z: app-versions 31012647428 at
v1.2.0failure → 31013564400 atv1.3.0success. This is what was blocking ~14 PHPMD PRs.Question 2: the pin must move WITH
quality.yml, or not at allThree separate desyncs in one day, all the same shape — the shared workflow is
@mainwhile the package is pinned:gh_slugify(gate-46 anchor resolution) → in no released tag, so consumers on any tag still run the old resolver. Counts measured with it present are not the counts CI produces.run:step is what made the workflow unresolvable #168 madequality.ymlinvoke${GITHUB_WORKSPACE}/gates/hydra-gates/scripts/axe-run.cjs— the workflow now reaches into the pinned package by path. That file exists only onmain. Latent today only because no repo setsenable-axe: true; the first one that does, on a tagged pin, gets a file-not-found.(3) is the decisive one. A workflow that executes a path inside the pinned package has made the two a single unit. Pinning one and floating the other is not a conservative choice — it is an unversioned interface, and it has now failed three times in a day.
Recommendation, in preference order:
quality.yml@vX.Y.Zandhydra-gates-ref: vX.Y.Zfrom the same tag. One bump wave moves both; a desync becomes impossible by construction.@main+hydra-gates-ref: main). Loses reproducibility but at least the halves always match.A moving
v1minor tag does not fix this. It reduces the bump waves but leaves the workflow and package on independent clocks, which is the actual defect.I cut two tags
v1.3.0=f7eaf2a— carries fix(gates): 16 gates reported PASS when their helper never ran — 2 are authorization gates #147/feat(quality): produce tests/axe/report.json so gate-33 (axe-core) can actually run #148/fix(hydra-gates): gate-7 follows delegation; gates 6/7 stop passing on an empty scope #149/fix(quality): two dead gates in the coverage ratchet — an artifact that never existed, and a job deleted by an unrelated failure #156/fix(gate-5): route-auth reported a resolution failure as a security finding, and never saw a camelCase route #162/fix(hydra-gates): a not-applicable gate is not a coverage gap — fix the accounting, then flip the flag #164. This is what the fleet is being rolled to, matching the already-merged doriath#160.v1.4.0=46cc1c8— additionally carries fix(gate-46): resolve anchors the way GitHub actually publishes them #165 (gh_slugify) and fix(quality): re-land axe DOM scoping, with the runner in a file — a 22 KBrun:step is what made the workflow unresolvable #168'saxe-run.cjs.I deliberately rolled v1.3.0, not v1.4.0, for fleet uniformity with the repo that already landed, and because v1.3.0 is what demonstrably fixes today's red. v1.4.0 is a strict superset and should be a separate, measured follow-up —
gh_slugifyreduces gate-46 findings (openconnector: 42 with it vs 109 without), so it makes repos greener, but that is a verdict change across 22 repos and deserves its own measurement rather than riding along on an urgent fix.One correction to my own earlier reporting in this thread
My first fallout table showed gate-22
manifest-validationnewly failing in 8 repos. That was my harness, not the repos —ajvwas absent locally, so the validator ran degraded and correctly refused to report a pass. CI installsajv. With it installed, gate-22 passes in all of them, and the corrected delta is the opposite of what I first had: 12 repos lose a gate-22 failure and 5 lose gate-7. Flagging it because it is the same class of error this issue is about — a measurement artifact that reads exactly like a finding.ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): switch the Hydra gates ON for the first time, pinned to …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0, which is what is …
feat(quality): stop pinning the gates package per repo, and gate main…
chore(ci): stop pinning hydra-gates — track the package at @main (#74)
chore(ci): stop pinning hydra-gates — track the package at @main (#129)
chore(ci): stop pinning hydra-gates — track the package at @main (#322)
chore(ci): stop pinning hydra-gates — track the package at @main (#132)
feat(gates,quality): diff-scoped gates, gate 19 on the change only, g…