Repo: ra8844/core (public fork of home-assistant/core), branch tailscale-oauth-client-credentials, commit 97076c15672d26773312dea45d889963bcbe3dbb, uploading via codecov-action v7 (codecov-cli), flag full-suite.
Coverage uploads are rejected at ingest with {"message":"Token required because branch is protected"} even though every UI signal says the upload should be accepted:
- The repo shows active (Configuration → General shows the "Deactivate" button in the Danger Zone).
- The org banner says "Your org no longer requires upload tokens. You can upload without a token."
- The upload was made with the repository upload token copied from that same Configuration page, and the CI log confirms it was passed (
upload-coverage -t <redacted>).
What we tried, all on the same run (https://github.com/ra8844/core/actions/runs/30637059898):
- Codecov API access token as the upload token →
{"message":"Repository not found"} (~14:47 UTC 2026-07-31)
- Global upload token →
{"message":"Token required because branch is protected"} (~14:55 UTC)
- Repository upload token → same "branch is protected" error (~15:03 UTC)
Additional context: a tokenless upload to this same repo/branch succeeded on 2026-07-20 (commit 7a4ff64, still visible on the dashboard — 100% of 194 lines). At some point after that, the repo showed as deactivated; after signing in on 2026-07-31 it shows active again. It looks like the ingest side has stale activation/token-requirement state that disagrees with what the UI reports.
Could you reconcile the repo's activation/token state, or explain what would make the repository's own upload token be rejected with a "token required" error?
Repo:
ra8844/core(public fork of home-assistant/core), branchtailscale-oauth-client-credentials, commit97076c15672d26773312dea45d889963bcbe3dbb, uploading via codecov-action v7 (codecov-cli), flagfull-suite.Coverage uploads are rejected at ingest with
{"message":"Token required because branch is protected"}even though every UI signal says the upload should be accepted:upload-coverage -t <redacted>).What we tried, all on the same run (https://github.com/ra8844/core/actions/runs/30637059898):
{"message":"Repository not found"}(~14:47 UTC 2026-07-31){"message":"Token required because branch is protected"}(~14:55 UTC)Additional context: a tokenless upload to this same repo/branch succeeded on 2026-07-20 (commit
7a4ff64, still visible on the dashboard — 100% of 194 lines). At some point after that, the repo showed as deactivated; after signing in on 2026-07-31 it shows active again. It looks like the ingest side has stale activation/token-requirement state that disagrees with what the UI reports.Could you reconcile the repo's activation/token state, or explain what would make the repository's own upload token be rejected with a "token required" error?