feat: set up codecov for the hardhat repository

[galargh]

• Because this PR includes a bug fix, relevant tests have been included.
• Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
• I didn't do anything of this.

---

This PR sets up Codecov for the Hardhat repository. It will allow us to track the following over time:

• unit test coverage
• test flakiness (beta)
• bundle size (with an asset breakdown)

The Codecov integration will also comment on PRs highlighting the changes to the above metrics in relation to the target branch.

⚠️ In this PR, I also remove our custom bundle comments. Instead, we'll rely on Codecov's bundle analysis. There is a slight regression as the comment from Codecov about the bundle size will not include the information about the number of dependencies. This information will only be available after clicking through to the bundle analysis details, also present in the comment. In my opinion, this is acceptable. Especially since, the codecov integration will allow us to track bundle size over time, something we didn't do before.

⚠️ Please note that the coverage tracking does not currently work for the ignition packages. After discussing this internally, I decided not to fix it now since the ignition packages are soon to be migrated to node test runner anyway. This migration will likely come with the coverage support out of the box.

TODO

• Install Codecov GitHub App for the hardhat repository
• Set the Default Branch / Branch Context to v-next in Codecov Repository Configuration
• *Copy the CODECOV_TOKEN from the Codecov Repository Configuration
• *Add the CODECOV_TOKEN secret to the Repository Secrets
• Maybe add the codecov.yml to the main branch (?) - I'm not 100% sure it's needed, let's try without it first

*Alternatively, we can set up the CODECOV_TOKEN for the entire organization by copying it from the Codecov Organization Configuration and adding the CODECOV_TOKEN secret to the Organization Secrets

[changeset-bot]

⚠️ No Changeset found

Latest commit: afe84ec

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hardhat	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 10, 2025 3:55pm