fix(codecov): 🐛 configure codecov-action v5 with token authentication#100
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
…e PyPI Co-authored-by: sheldonhull <3526320+sheldonhull@users.noreply.github.com>
|
@copilot I don't like this approach. see guide here: https://github.com/codecov/codecov-action |
…n with token Co-authored-by: sheldonhull <3526320+sheldonhull@users.noreply.github.com>
Reverted aqua changes and updated to use codecov-action with CODECOV_TOKEN. SHA verified as correct for v5.5.1. (commit: 08e3708 reverted, new changes in next commit) |
Problem
The codecov-action v5 dynamically downloads the Codecov CLI binary from
cli.codecov.ioduring test runs, which can cause tests to fail due to:This results in flaky test runs and CI failures unrelated to actual code changes.
Solution
This PR resolves the issue by using the official codecov-action v5.5.1 with proper token authentication as recommended in the codecov-action documentation.
Changes
.github/workflows/test.yml5a1091511ad55cbe89839c7260b706298ca349f7token: ${{ secrets.CODECOV_TOKEN }}parameter for authenticationBenefits
The codecov-action v5 handles downloading and managing the CLI binary automatically, providing a reliable upload mechanism without requiring custom tooling configuration.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.