Join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
Both the Backend CI and Soroban Contracts CI jobs run a final codecov/codecov-action@v5 step with fail_ci_if_error: true. When CODECOV_TOKEN is missing/invalid (as it currently is), that step fails and turns the whole job red even when build, tests, and coverage all passed. Right now the contracts job gets all the way through build + 95 tests + tarpaulin coverage and only dies on this upload.
Acceptance criteria
Files to touch
.github/workflows/ci.yml (the two Upload * coverage to Codecov steps)
Out of scope
- Fixing the backend test failures themselves (separate issue)
Join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
Both the Backend CI and Soroban Contracts CI jobs run a final
codecov/codecov-action@v5step withfail_ci_if_error: true. WhenCODECOV_TOKENis missing/invalid (as it currently is), that step fails and turns the whole job red even when build, tests, and coverage all passed. Right now the contracts job gets all the way through build + 95 tests + tarpaulin coverage and only dies on this upload.Acceptance criteria
CODECOV_TOKENas a repo secret and confirm upload succeeds, ORfail_ci_if_error: falseon both Codecov steps so coverage upload is best-effortFiles to touch
.github/workflows/ci.yml(the twoUpload * coverage to Codecovsteps)Out of scope