Commit b24ea4e
fix(ci): correct 3 secret-name mismatches causing silent no-ops
Found during a post-breach credential audit: these workflows reference
secret names that don't exist on this repo, so the affected steps
silently degrade (empty token / fallback) instead of failing loudly.
- supervised-fleet-scan.yml: referenced secrets.FLEET_SCAN_PAT, which
has never existed here — only HYPATIA_SCAN_PAT is configured, and
its scope (Contents+Dependabot alerts read) is exactly what this
step's own comment says it needs. Pointed it at the secret that
actually exists.
- inbox-steward.yml "Validate PRs": referenced secrets.FARM_PAT (never
configured). This step only reads check-runs/reviews/PRs on this
same repo — it never needed a cross-repo PAT. Switched to
secrets.GITHUB_TOKEN, which is sufficient and always present.
- inbox-steward.yml "Send dispatch to Hypatia": same missing FARM_PAT
reference, but this step genuinely dispatches cross-repo, so it
keeps the same PAT-with-fallback shape — just pointed at
FARM_DISPATCH_TOKEN, the secret that's actually meant to carry that
capability (currently dead pending redistribution of the new
FARM_DISPATCH_PAT value, tracked separately).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>1 parent bcd8a4c commit b24ea4e
2 files changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
166 | 166 | | |
167 | 167 | | |
168 | 168 | | |
169 | | - | |
| 169 | + | |
170 | 170 | | |
171 | 171 | | |
172 | 172 | | |
| |||
384 | 384 | | |
385 | 385 | | |
386 | 386 | | |
387 | | - | |
| 387 | + | |
388 | 388 | | |
389 | 389 | | |
390 | 390 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
46 | 46 | | |
47 | 47 | | |
48 | 48 | | |
49 | | - | |
| 49 | + | |
50 | 50 | | |
51 | 51 | | |
52 | 52 | | |
53 | 53 | | |
54 | 54 | | |
55 | 55 | | |
56 | | - | |
| 56 | + | |
57 | 57 | | |
58 | 58 | | |
59 | 59 | | |
| |||
0 commit comments