fix(deps): regenerate lockfile with duplicate undici@8.12.1 key #276
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!276
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-duplicate-undici-lockfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
#272 and #273 each added an
undici@8.12.1entry topnpm-lock.yaml, and both merged. The lockfile onmainnow has duplicate mapping keys (packages:andsnapshots:). pnpm reports:Then pnpm re-resolves everything from scratch on every
pnpm install, which leaves a ~2k-line lockfile diff in every checkout. This is the "two PRs pass alone but breakmaintogether" case from CLAUDE.md.Fix
Regenerated the lockfile and ran
pnpm dedupe. Because pnpm resolved everything again, some packages moved to newer versions inside their existing ranges. Examples:@sentry/*11.7.0 → 11.8.0,i18next26.4.4 → 26.4.7,react-i18next17.0.16 → 17.0.20.Verification
pnpm install --frozen-lockfilegives no warning and leaves the tree cleanpnpm typecheckpassespnpm testpasses (14/14)pnpm buildpasses🤖 Generated with Claude Code