upgrade codecov action to v7#54
Merged
Merged
Conversation
yarn set version berry was upgrading to the latest yarn (now 4.16.0), which generates lockfile format version 10. The existing lockfiles are version 9 (matching packageManager: yarn@4.14.1). This caused yarn install --immutable to fail on every PR. With corepack enabled, yarn uses the version pinned in packageManager directly, so the set-version step is unnecessary. Also gitignore PnP artifacts (.pnp.cjs, .yarn/) for both sample projects.
chrisbc
approved these changes
Jun 9, 2026
chrisbc
left a comment
chrisbc
left a comment
Member
There was a problem hiding this comment.
LGTM @chrisdicaprio - assuming the berry version update is now redundant
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
upgrade to codecov v7. v5 was often failing to get GPG key