Fix Codecov PGP key fetch in coverage upload (release/26.8) - #22964
Conversation
Codecov rotated their Keybase username from codecovsecurity to codecovsecops (the new URL serves the same key fingerprint 27034E7FDB850E0BBC2C62FF806BB28AED779869). The old URL now returns a 32-byte 404 body that curl was happily piping into gpg, breaking the import and aborting run-unit-tests.sh under `set -e` before merge_junit_reports could run. Also add `--fail --silent --show-error` so any future move surfaces as a curl failure with a clear message instead of an opaque gpg error. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Generated by 🚫 Danger |
|
|
|
|
✅ Codecov report verified via APIConfirmed the coverage upload now works end-to-end. Queried the Codecov API for commit
PR comparison (Codecov This confirms the keybase URL fix ( Full report: https://app.codecov.io/gh/wordpress-mobile/WordPress-Android/pull/22964 Note: the report is uploaded and processed on Codecov, but no Codecov status check/comment is auto-posted on the GitHub PR — that's a separate Codecov GitHub-integration config matter, unrelated to this script fix. |


Backport of #22963 to
release/26.8.Summary
CI was failing in the
Uploading code coveragestep becausecurl https://keybase.io/codecovsecurity/pgp_keys.ascnow returns a 32-byte HTTP 404 (SELF-SIGNED PUBLIC KEY NOT FOUND). That body gets piped intogpg --import, gpg fails with "no valid OpenPGP data found", andset -eaborts the rest of the run-unit-tests script beforemerge_junit_reportsruns.Codecov appears to have renamed their Keybase account from
codecovsecuritytocodecovsecops. The new URL serves the same signing key (fingerprint27034E7FDB850E0BBC2C62FF806BB28AED779869, key IDED779869).Changes
codecovsecurity→codecovsecops.--fail --silent --show-errorto thecurlcall so the next time this URL moves, curl exits non-zero with a clear error instead of silently piping a 404 page into gpg.Test plan