Skip to content

ci(ci-gate): re-pin the cicd-suite gate to 09878f2 (emoji-safe status descriptions) - #54

Open
hyperpolymath wants to merge 2 commits into
mainfrom
claude/intelligent-johnson-i64bfk
Open

hyperpolymath wants to merge 2 commits into
mainfrom
claude/intelligent-johnson-i64bfk

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

Re-pins the CI gate reusable workflow from d2140a5a789e4ebec52f1bab0074181012660c3b to 09878f2a2c0a8907cc69fe48973ea604753ecab1 (hyperpolymath/proven-cicd-and-workflows#144). The old pin posts CI/gate = failure falsely when a workflow name contains an emoji, because GitHub rejects 4-byte UTF-8 in a status description. That false red was seen on #48. Between the two pins the tamper guard workflow changed by one line, and ci-gate.yml gained the emoji-safe description handling.

09878f2 is a commit on an UNMERGED suite branch (#144 is stacked on #139), as d2140a5 was. A second re-pin therefore follows #139's squash merge.

This PR touches gate files (ci-gate.yml, ci-gate-tamper-guard-caller.yml), so the tamper guard may fail guard / check until an admin applies the gate-change-approved label. Agents do not apply it.

Changes

  • .github/workflows/ci-gate.yml (2 uses: lines) and .github/workflows/ci-gate-tamper-guard-caller.yml (1 line): new SHA; the # cicd-suite ... trailing comments are kept.
  • .github/workflows/actions.lock: both workflow entries, the dependency key and its commit: sha1-... record. owner_id, repo_id and ref are unchanged.
  • tests/workflows/actions_lock_sha_refs_test.sh (case table row) and tests/workflows/squabble_gate_test.sh (SUITE_PIN): they assert the live pin.
  • CHANGELOG.adoc: new entry. The older entry that mentions d2140a5 is history and is untouched.

RSR Quality Checklist

Required

  • Tests pass (the workflow tests listed below)
  • Code is formatted (just fmt or equivalent): not run, no formatted source changed
  • Linter is clean: not run, no source changed
  • No banned language patterns
  • No unsafe blocks without // SAFETY: comments (none added)
  • No banned functions
  • SPDX license headers untouched
  • No secrets, credentials, or .env files included

As Applicable

  • CHANGELOG or release notes updated
  • Other items: not applicable

Testing

Run locally on this branch, all exit 0:

  • scripts/check-lock-sync.sh: in sync and transitively closed.
  • tests/workflows/squabble_gate_test.sh: 144 passed, 0 failed.
  • tests/workflows/actions_lock_sha_refs_test.sh: 27 PASS lines.
  • tests/workflows/check_lock_sync_test.sh: 26 PASS lines.
  • tests/workflows/ci_gate_test.sh and tests/workflows/validate_workflows_test.sh: exit 0.

What is NOT proven

  • That the emoji fix works in a live run here: that is only seen once CI/gate runs on this PR.
  • That 09878f2 will survive the squash merge of #139: it is not on a protected branch.
  • actionlint and just test && just quality were not run.
  • The lock entry is hand-maintained (gh actions-lock cannot lock cross-repository reusables), so check-lock-sync.sh is its only authority.

Screenshots

N/A


Generated by Claude Code

… descriptions)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDiRggj6apeRQKPpAVR

Copy link
Copy Markdown
Owner Author

Two checks failed on 78c6920: Proven 3-outcome test & bench suite and gate-pr / CI gate. The re-pin did not cause either.

  • Bench suite: oven-sh/setup-bun failed fetching api.github.com/repos/oven-sh/bun/git/refs/tags with HTTP 403, "API rate limit exceeded for installation". That happens before any repository code runs.
  • CI gate: the gate's first status post hit the same 403 ("could not publish the re-run pending status; NO VERDICT WAS PRODUCED"). The failure handler's own post was rate-limited too.

The limit belongs to the GitHub App installation and resets on GitHub's hourly window. Several CI gates were polling across the estate at the same time, which probably used it up. I'll re-run the failed jobs once after the reset and nothing more.


Generated by Claude Code

Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
@sonarqubecloud

Copy link
Copy Markdown

Copy link
Copy Markdown
Owner Author

The failures on c4e5729 (the merge of main) all come from the GitHub App installation's API rate limit, not from the re-pin:

  • Canon lockstep: curl: (22) ... error: 403 while fetching the deed. The job then reports this as "no resource-algebra_chora.deed", but the file exists; the fetch was refused.
  • Proven 3-outcome test & bench suite: oven-sh/setup-bun got HTTP 403, "API rate limit exceeded for installation".
  • Squabble CI chains & required-context gate: squabble_gate_test passes 144/0 and check-required-contexts reports OK. Only the installer step fails ("release not found"). The same job also failed on main's latest push (7186d70, run 44301668233).
  • Hypatia, CodeQL analyze: in the earlier runs these failed on SARIF uploads refused by the rate limit. The same is likely here.
  • CI/gate: correctly reports the bench and Squabble failures above. It runs the old #139 gate code, which also reported "could not read the workflow runs" at 11:56.

After the merge the diff is consistent: the callers, actions.lock and both test fixtures move from 4e9e680 (#139's squash, without the 4-byte filter) to 09878f2 (with it). I'm not re-running anything while the quota is exhausted. suite#148 removes the fan-out that keeps using it up.


Generated by Claude Code

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.

3 participants