Skip to content

chore(ci): stop pinning hydra-gates — track the package at @main - #1159

Merged
rubenvdlinde merged 3 commits into
developmentfrom
chore/hydra-gates-ref-v1.4.0
Aug 6, 2026
Merged

rubenvdlinde merged 3 commits into
developmentfrom
chore/hydra-gates-ref-v1.4.0

Conversation

@rubenvdlinde

@rubenvdlinde rubenvdlinde commented Aug 5, 2026 •

Copy link
Copy Markdown
Contributor

What changed

This PR started life as a pin bump (hydra-gates-ref: v1.3.0 -> v1.4.0). It now removes the hydra-gates-ref line entirely so this caller inherits the shared workflow's default.

       enable-hydra-gates: true
-      hydra-gates-ref: v1.4.0

enable-hydra-gates: true is unchanged. enable-axe remains unset. The comment block that justified the pin is replaced with a short note explaining why there is deliberately no pin.

Why

ConductionNL/.github/.github/workflows/quality.yml already defaults hydra-gates-ref to main, and this repo consumes quality.yml at @main. Overriding the input was the only thing holding the gates package still. Drop the override and both sides move together — a gate fix reaches this repo without a commit in this repo.

Bumping the pin is a treadmill: it works until the next fix lands upstream, and between bumps the repo is running whatever the gates package looked like on the day someone last remembered.

A pin is a silent expiry date on every upstream fix. We have paid for that twice:

  • .github#159 — 22 repos sat pinned on v1.0.1, which predated the gate fixes. 16 gates were dead fleet-wide and every one of them reported PASS. A gate that never runs emits a tick identical to one that did, so nothing in any repo's CI history showed it.
  • .github#173 — the shared side flipped a default at @main while the package stayed pinned per caller. Old pinned runners did not carry the coverage accounting the new default assumed, so they went red on gates they had no subject matter for.

The two failures are opposite shapes of the same split: shared workflow at @main, package pinned. Removing the pin closes both.

Rollback

  • For everyone: revert on ConductionNL/.github main. One commit reaches the whole fleet — which is the point.
  • For this repo only: set hydra-gates-ref: explicitly again, with a comment saying why this repo needs to hold still. The input is still honoured; it just is not the default posture.

Safety net

ConductionNL/.github#177 adds the resolve probe plus the gates package suite gating .github main, so a broken package cannot reach main unnoticed now that consumers track it.

A pinned `hydra-gates-ref` is a silent expiry date on every upstream fix:
this repo cannot receive a gate-package change until this line moves.

v1.4.0 is the latest tag and the first one that carries
`hydra-gates/scripts/axe-run.cjs` (verified absent at v1.3.0), so it is
also the first that has ConductionNL/.github#168 axe DOM scoping and
ConductionNL/.github#165 gate-46 fix.

`enable-axe` is deliberately NOT enabled in this commit. Ordering matters:
the ref lands first, enabling axe is a separate decision.
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openconnector @ 9f8669f

Check PHP Vue Security License Tests
lint ✅
phpcs ✅
phpmd ✅
psalm ✅
phpstan ✅
phpmetrics ✅
eslint ✅
stylelint ✅
build ✅
build ✅
check-specs ✅
test-l10n ✅
composer ✅ ✅ 153/153
npm ✅ ✅ 692/692
PHPUnit ✅
Newman ✅
Playwright ✅
Hydra gates ✅

Quality workflow — 2026-08-05 22:04 UTC

Download the full PDF report from the workflow artifacts.

Removes `hydra-gates-ref` entirely instead of moving it v1.3.0 -> v1.4.0.
The shared workflow already defaults the input to @main, and this repo
consumes `ConductionNL/.github/.github/workflows/quality.yml@main`, so both
sides now move together: a gate-package fix reaches this repo with no commit
here.

A pin is a silent expiry date. 22 repos sat on v1.0.1 while 16 gates were
dead fleet-wide and every one of them reported PASS (.github#159), and a
default flipped at @main later reached those same old runners and failed them
on gates they had no subject matter for (.github#173). Bumping the pin is a
treadmill that reintroduces the same failure mode on the next release.

The pin-justifying comment block is replaced with a short note saying why
there is no ref here and how to reintroduce one deliberately. The rationale
for `enable-hydra-gates: true` is kept, as is `enable-axe` being left off and
this repo's explicit `hydra-gates-require-full-coverage: false`.
@rubenvdlinde rubenvdlinde changed the title chore(ci): move hydra-gates-ref v1.3.0 -> v1.4.0 chore(ci): stop pinning hydra-gates — track the package at @main Aug 6, 2026
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openconnector @ d2b0f8b

Check PHP Vue Security License Tests
lint ✅
phpcs ✅
phpmd ✅
psalm ✅
phpstan ✅
phpmetrics ✅
eslint ✅
stylelint ✅
build ✅
build ✅
check-specs ✅
test-l10n ✅
composer ✅ ✅ 153/153
npm ✅ ✅ 692/692
PHPUnit ✅
Newman ✅
Playwright ✅
Hydra gates ✅

Quality workflow — 2026-08-06 06:05 UTC

Download the full PDF report from the workflow artifacts.

…is failing this repo now

development moved the pin to v1.5.0 while this branch removes it. Resolved in
favour of removing it: a pin is what broke, and v1.5.0 is not a better pin.

Since this branch was opened, the pinned-package-vs-floating-@main desync
produced its most acute form yet. quality.yml@main now executes three gate
helpers BY NAME — check_spec_anchors.py, check_form_labels.py and
check_license_triangle.py — and NO tag before v1.5.0 contains any of them, so
the Hydra Gates job here fails at "Verify the pinned gates package satisfies
this workflow", before a single gate runs, with the workflow's own message:
"This is NOT a code-quality finding about your repository."

Verified by DIRECTORY LISTING of each tag rather than per-file lookups. Those
answered "present" UNIFORMLY across v1.0.0..v1.5.0 — and uniformity across
independent inputs is a statement about the instrument, not the inputs. The
listing gives 0 of 3 at every tag through v1.4.0 and 3 of 3 at v1.5.0.

Unpinning also picks up .github#179 (v1.5.1): on a push to `development`,
`origin/development` IS `HEAD`, so the diff was empty by construction —
<= v1.4.0 passed over it (permanently green) and v1.5.0 refused with exit 99
(permanently red). The scope is now `github.event.before...HEAD`, what the push
actually changed, with exit 99 kept only for the cases that genuinely cannot be
scoped.
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openconnector @ 8d552b5

Check PHP Vue Security License Tests
lint ✅
phpcs ✅
phpmd ✅
psalm ✅
phpstan ✅
phpmetrics ✅
eslint ✅
stylelint ✅
build ✅
build ✅
check-specs ✅
test-l10n ✅
composer ✅ ✅ 153/153
npm ✅ ✅ 692/692
PHPUnit ✅
Newman ✅
Playwright ✅
Hydra gates ✅

Quality workflow — 2026-08-06 06:41 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit dfc8ee5 into development Aug 6, 2026
35 checks passed
@rubenvdlinde
rubenvdlinde deleted the chore/hydra-gates-ref-v1.4.0 branch August 14, 2026 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant