chore: sync bun.lock trustedDependencies after dropping lefthook - #2084
Merged
Conversation
The lockfile still listed lefthook under trustedDependencies after it was removed from the workspace package.json files, so every bun install reconciled it away and left the lockfile dirty. Regenerated with bun install so the lock matches package.json; no dependency versions change. --frozen-lockfile did not flag this because trustedDependencies metadata drift does not fail a frozen install.
Contributor
|
No reviewable files after applying ignore patterns. |
Contributor
✅ Tests passed — 2520/2524
|
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
1 participant
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.
What
Regenerates
packages/browseros-agent/bun.lockso itstrustedDependenciesmatches the workspace package.json.Why
PR #2074 removed
lefthookfromtrustedDependenciesin the package.json files but did not regenerate the lockfile, sobun.lockstill listedlefthookthere. Everybun installreconciled it away, leaving the lockfile dirty in every worktree.--frozen-lockfiledid not catch it becausetrustedDependenciesmetadata drift does not fail a frozen install (only dependency-graph changes do).How
bun installon a clean checkout. The only change is dropping the stalelefthookline from the lock'strustedDependencies; no dependency versions change, andbun install --frozen-lockfilereports no changes against the updated lock.