Skip to content

Add the governance gate; move to the shared workflow tag - #2

Merged
lessevv merged 5 commits into
mainfrom
chore/spec-alignment
Jul 27, 2026
Merged

Add the governance gate; move to the shared workflow tag#2
lessevv merged 5 commits into
mainfrom
chore/spec-alignment

Conversation

@lessevv

@lessevv lessevv commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Spec: REPO-R1, REPO-R5, REPO-R7, GOV-R12

The gate was missing

REPO-R1 requires every repository to call the shared governance gate. This one
called hygiene, security, sign-off, commit lint, the reference comment and the
labeler — but not the gate itself, so a change here could merge citing nothing.

Shared calls move to @v1

Per ADR-0021:
v1 moves forward as fixes merge in the spec repository, so a shared fix still
propagates in one merge, but a breaking change to a calling interface cuts v2
and this repository migrates deliberately rather than failing the moment
something lands there.

spec-references is now skipped for fork pull requests, whose token cannot
write the comment it exists to post.

CODEOWNERS

REPO-R5 requires an ownership file generated from the maintainer registry.
This repository had none, so no path had a declared owner and the triage
workflow's assignee lookup had nothing to read.

Pre-existing failures fixed

Turning the full gate on surfaced three failures that were already there:

  • labeler had no .github/labeler.yml, so the action 404'd on every run.
  • osv-scanner reports 19 known vulnerabilities in the pinned Astro version.
  • typos findings in the site content.

Requires beatrax-app/spec#1, merged and tagged v1.

lessevv added 2 commits July 27, 2026 20:14
REPO-R1 requires every repository to call the shared governance gate.
This one called hygiene, security, sign-off, commit lint, the reference
comment and the labeler — but not the gate itself, so a change here could
merge citing nothing.

The reusable calls move from commit pins to the v1 tag, per ADR-0021:
v1 moves forward as fixes merge in the spec repo, and a breaking change
to a calling interface cuts v2 so this repo migrates deliberately rather
than failing the moment something lands there.

spec-references is now skipped for fork pull requests, whose token cannot
write the comment it exists to post.

Spec: REPO-R1, REPO-R7
Signed-off-by: Wessel Verheij <info@nightworks.io>
REPO-R5 requires every repository to carry an ownership file generated
from the maintainer registry. This one had none, so no path had a
declared owner and the triage workflow's assignee lookup had nothing to
read.

Spec: REPO-R5
Signed-off-by: Wessel Verheij <info@nightworks.io>
@github-actions

github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown

📎 Spec references

This PR cites the following spec identifiers:

  • REPO-R1 — Every repository MUST call the shared governance gate, and no behavioural change may merge without a citation that resolves on the canoni…
  • REPO-R5 — Every repository's CODEOWNERS MUST be generated from the single maintainer registry and MUST NOT be edited by hand.
  • REPO-R7 — Every third-party action MUST be pinned to a full commit hash with an inline version comment; first-party reusable workflows MUST be refe…
  • GOV-R12 — Routine maintenance — dependencies, formatting, pipeline mechanics — MUST cite this identifier.

Updated automatically on each push.

lessevv added 2 commits July 27, 2026 20:31
Two of the shared checks have been running against this repository without
the configuration they need, and failing on every pull request.

The auto-labeler had no `.github/labeler.yml`, so it 404'd looking for one
rather than labelling anything. The map is added, pointing this repo's paths
at the canonical label set.

The spell-checker was reading the Dutch half of the site as a wall of typos.
Those files are excluded rather than allow-listed word by word: adding fifty
Dutch words to an English dictionary would make the checker useless for the
English copy it exists to protect.

Spec: GOV-R12
Signed-off-by: Wessel Verheij <info@nightworks.io>
The dependency scanner reports nineteen known vulnerabilities against the
pinned Astro version, five of them rated high. Clearing all of them needs
7.1.x, which is two majors ahead of where this sat.

Taken in one step rather than staged, because the intermediate versions each
leave some of the nineteen open and there is no partial state worth landing.

Verified: `astro check` reports zero errors across 69 files, and the site
builds all 33 pages.

Spec: GOV-R12
Signed-off-by: Wessel Verheij <info@nightworks.io>
@github-actions github-actions Bot added ci Pipelines, workflows, and release engineering dependencies Dependency update (Renovate / Dependabot) labels Jul 27, 2026
Astro 7 requires Node 22.12 or newer. The workflows pinned 20 and the
`.nvmrc` said the same, so the upgrade type-checked and built locally on
a newer runtime while failing in CI — the gap the `.nvmrc` exists to
close.

Both workflows and the version file move together, so a contributor
running `nvm use` gets what CI runs.

Spec: GOV-R12
Signed-off-by: Wessel Verheij <info@nightworks.io>
@lessevv
lessevv merged commit 1637283 into main Jul 27, 2026
12 checks passed
@lessevv
lessevv deleted the chore/spec-alignment branch July 27, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Pipelines, workflows, and release engineering dependencies Dependency update (Renovate / Dependabot)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant