From 632a9e0de2c7106c23150738eb86faa6b864f6e9 Mon Sep 17 00:00:00 2001 From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com> Date: Thu, 6 Aug 2026 04:03:13 +0100 Subject: [PATCH] fix(ci): repair workflows made unparseable by a blind permissions insertion MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit These workflow files are not valid YAML, so they have NEVER run. GitHub Actions rejects the file before creating any job: the run is recorded as `failure` with no jobs, no log and no check run, and `gh pr checks` shows no row at all. A red mark with nothing behind it to read. The cause is a sweep that added permission declarations by LINE POSITION rather than by parsing the document. Two invalid shapes resulted. permissions: read-all actions: read <- a mapping indented under a SCALAR value `read-all` is a scalar and cannot take children. It also already grants everything `actions: read` would, so the orphaned line is dropped and nothing is lost. on: permissions: contents: read <- two colons on one line, and push: `permissions` is not a valid key here Dropped entirely. VERIFIED, not assumed. Every workflow in this repository parses after the change, and the repairer refuses to write any file that does not parse and still contain jobs afterwards. Where a job-level permissions line was removed, a top-level `permissions:` remains and is read-only, so nothing is widened — and if none remained the tool reports that rather than inventing one, because guessing a permission set is how you silently over-grant. ESTATE CONTEXT: 67 repositories and 100 workflow files are in this state. The most frequently broken file is workflow-linter.yml, in 22 repositories — the workflow whose job is to lint workflows was itself unparseable, so it never ran and never caught this. Detection is being added upstream so it cannot recur invisibly: a strict YAML loader in the governance reusable (hyperpolymath/standards#582). Ordinary validation cannot see this class of fault, because yaml.safe_load accepts duplicate keys and only a full parse catches the malformed indentation. EXPECT THIS REPOSITORY TO GET LOUDER. Workflows that have been failing silently will now actually run, and some will find real problems. Co-Authored-By: Claude Fable 5 Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com> --- .github/workflows/workflow-linter.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/workflows/workflow-linter.yml b/.github/workflows/workflow-linter.yml index 9ad08b3..67b6a82 100644 --- a/.github/workflows/workflow-linter.yml +++ b/.github/workflows/workflow-linter.yml @@ -11,7 +11,6 @@ on: - '.github/workflows/**' permissions: read-all - actions: read jobs: lint-workflows: