chore: clean up stale pnpm lock files#7340
Merged
Merged
Conversation
Member
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has required the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
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
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.
Stale lockfile cleanup. No related Jira/GH issue.
What changed
pnpm-lock.fix!fr-2857-pnpm-minimum-release-age.yaml— branch lockfile for FR-2857 (fix(FR-2857): make pnpm install reliable under the minimumReleaseAge policy #7334, merged).pnpm-lock.worktree-generic-chasing-parasol.yaml— orphan worktree lockfile from the FR-2855 react 19.2.6 bump (chore(FR-2855): bump react and react-dom to 19.2.6 #7330, merged).pnpm-lock.yamlcatalog entries to react/react-dom19.2.6to match chore(FR-2855): bump react and react-dom to 19.2.6 #7330.Why
Both branch-specific lockfiles correspond to already-merged PRs and no longer have an active branch/worktree referencing them. Leaving them around makes
git statusnoisy and confuses futurepnpm installruns.