[BUG] After force pushing to a remote branch on Github to override a commit, the branch no longer gets updated on app.codecov.io

Describe the bug

1. I force pushed to my repository's dev branch to edit the message for this commit.
2. The new commit in dev is here.
3. The latest commit in dev in this page still points to the old commit cb8e8dc.
4. Github Actions did upload the code coverage report for the new commit to codecov.io in this workflow run. The code coverage is accessible here. But it does not show up for dev.

This is an issue because I have outstanding pull requests where the code coverage report's base branch is using that old commit. For example, this dependabot PR's code coverage report is based off of the old commit cb8e8dc instead of the new one. It shows a misleading diff with C code changes that are the same as in the new commit 6f9c95df.

To Reproduce
Steps to reproduce the behavior:

1. For a commit in a repository, edit the commit message and force push the remote branch.
2. Check the code coverage page for that branch to see if the old commit was overwritten by the new one.

Expected behavior
The code coverage page for the dev branch should show the new commit 6f9c95df.

Regression
This is a regression.

Screenshots
N/A

Product Area
Code coverage

Versions

• OS: ubuntu-22.04
• Git Host: GitHub
• CI/CD: GitHub Actions
• Uploader: codecov-action@5a1091511ad55cbe89839c7260b706298ca349f7 # v5.5.1

Commit and CI link
See description

Additional context
N/A

Start with the force-push reproduction described in the issue and inspect the linked GitHub Actions upload run, then compare the old and new commit pages on Codecov. The fix is complete when the dev branch points to commit 6f9c95df and dependent pull-request coverage uses that commit rather than cb8e8dc.