chore: add Claude Code GitHub Actions and Codecov OIDC permission - #214
Merged
Conversation
its-mash
force-pushed
the
chore/introduce-claude-and-oidc-token
branch
from
July 15, 2026 01:43
8a2afda to
c6cde01
Compare
its-mash
changed the title
added 2 commits
July 15, 2026 09:59
`@latest` is a moving tag, so a broken upstream release rolls into CI unreviewed — v1.6.2 shipped broken and was superseded three days later. Pin to v1.6.3 by SHA. Bump the cache `version` to rotate the key: a 6 KB entry had been saved under the old one, which the action restored as a hit and then skipped installing libglib2.0-dev, failing rust-check and ts-check on every branch.
The runner image ships an apt index from its build date (2026-06-24), and
cache-apt-pkgs-action's update_apt_lists_if_stale only runs under nektos/act
-- it guards on ACT=true, so on real runners it is a no-op. Its premise
("GitHub Actions runners have fresh package lists") does not hold.
Ubuntu published pipewire 1.0.5-1ubuntu3.3 and removed 3.2 from the pool, so
apt resolved a .deb that 404s. The action runs apt-fast install without
checking its exit code, so the failure was swallowed: it cached 0 packages as
a 6 KB entry, which every later run restored as a hit and then skipped the
install entirely -- leaving libglib2.0-dev absent and failing rust-check and
ts-check on every branch, including main.
Refreshing the index first makes apt resolve debs that actually exist.
Merged
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Repo tooling only — no application code touched.
claude.yml(mention-triggered assistant) andclaude-code-review.yml(automated PR review).id-token: writeto CI permissions. Without itcodecov/codecov-action@v5fails withCould not fetch an OIDC token.main— see below.The CI breakage
Since ~01:07 today every job on every branch failed, including a Dependabot PR that only bumps an npm package. Root cause was a poisoned apt cache: a 6 KB entry (a healthy one is hundreds of MB) sat under key
cache-apt-pkgs_fdcf5a845111e7ece6636e1a64892e8cscoped torefs/heads/main.awalsh128/cache-apt-pkgs-actionrestored it, reportedCache Size: ~0 MB (6324 B), treated it as a hit and skipped installinglibglib2.0-dev. Everything downstream fell over:rust-check— failed at the glib verification stepts-check—pnpm lintshells into cargo, which can't findglib-2.0.pctest-report— no artifacts from the jobs aboveCaches scoped to
mainare readable from every PR branch, so one bad entry poisoned everything.Fixes
versionbumped (1.1→1.2,1.3→1.4) to rotate the key, so a stale entry under the old key can't come back.@latest, a moving tag — upstream's v1.6.2 is literally titled "(broken, use v1.6.3)", and a future bad release would roll in unreviewed.Notes
chore:so release-please keeps them out of the release notes.main(so they benefit almost nothing); andts-checkpassesverify_glib: falsedespite running cargo, which is what turned this into a confusing deep failure instead of a fast, clear one.