Migrating CI from the Bash Uploader to the Codecov Uploader binary: safe rollback and unclear patch status behavior

We are moving a CI pipeline off the deprecated Bash Uploader onto the standalone Codecov Uploader binary, pinned to a specific release with SHA checksum verification. The upload step itself is stateless, so my assumption is that reverting the pinned version restores reporting if the new release misbehaves, and any coverage reports generated during the outage can simply be re-uploaded later.

What is less clear is the configuration side. Our codecov.yml defines project and patch status checks, and some patch checks use informational: true together with carryforward flags for partial builds. After the migration I want uploads and statuses to behave identically to before, but I am unsure whether the pinned uploader version treats these settings the same way the Bash Uploader did, and whether a misconfigured target could block merges even when uploads succeed.

Specifically:

• Is reverting the pinned uploader version sufficient for a clean rollback, or are there server-side or codecov.yml changes that must be reverted alongside it?
• Do informational: true patch checks combined with carryforward flags produce consistent patch-coverage results across uploader versions, or does this need to be verified empirically per release?
• What is the recommended way to validate codecov.yml and status check behavior on a test pull request before rolling the migration out to all branches?