fix(deps): re-sync yarn.lock with package.json (develop backport)#3193
Merged
fix(deps): re-sync yarn.lock with package.json (develop backport)#3193
Conversation
The lockfile carried stale entries for packages removed across the overhaul series (ethers, @ethersproject, @hyperlane-xyz/*, @lifi/widget, @livepeer/*, etc.) so CI's 'yarn install --immutable' check has been failing since the staging→master merge with: YN0028: The lockfile would have been modified by this install, which is explicitly forbidden. Same failure was blocking Netlify's production deploy — it runs the same immutable install before invoking nx build, and the build never ran on master since 22:07 UTC. Plain regen via 'yarn install'. -467 lines, all dead-package entries.
✅ Deploy Preview for tangle-dapp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for tangle-leaderboard ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for tangle-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Backport of #3191. Same lockfile drift hit develop after the overhaul series merged but the master hotfix landed via a cherry-pick. Keeping develop clean so the next promote doesn't reintroduce the YN0028 failure.