fix(deps): regenerate lockfile with duplicate undici@8.12.1 key #276

Merged
ullrich merged 1 commit from fix-duplicate-undici-lockfile into main 2026-10-17 10:26:25 +00:00
Owner

Problem

#272 and #273 each added an undici@8.12.1 entry to pnpm-lock.yaml, and both merged. The lockfile on main now has duplicate mapping keys (packages: and snapshots:). pnpm reports:

[WARN] Ignoring broken lockfile ... duplicate mapping key: undici@8.12.1

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 break main together" 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, i18next 26.4.4 → 26.4.7, react-i18next 17.0.16 → 17.0.20.

Verification

  • pnpm install --frozen-lockfile gives no warning and leaves the tree clean
  • pnpm typecheck passes
  • pnpm test passes (14/14)
  • pnpm build passes
  • e2e not run locally

🤖 Generated with Claude Code

## Problem #272 and #273 each added an `undici@8.12.1` entry to `pnpm-lock.yaml`, and both merged. The lockfile on `main` now has duplicate mapping keys (`packages:` and `snapshots:`). pnpm reports: ``` [WARN] Ignoring broken lockfile ... duplicate mapping key: undici@8.12.1 ``` 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 break `main` together" 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, `i18next` 26.4.4 → 26.4.7, `react-i18next` 17.0.16 → 17.0.20. ## Verification - `pnpm install --frozen-lockfile` gives no warning and leaves the tree clean - `pnpm typecheck` passes - `pnpm test` passes (14/14) - `pnpm build` passes - e2e not run locally 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(deps): regenerate lockfile with duplicate undici@8.12.1 key
All checks were successful
CD Staging / Build & Push journal Image (pull_request) Has been skipped
CD Staging / Build & Push planner Image (pull_request) Has been skipped
CD Staging / Deploy Staging (pull_request) Has been skipped
CD Staging / Deploy PR Preview (pull_request) Has been skipped
CI / Dockerfile Package Check (pull_request) Successful in 5s
CI / Security Scan (pull_request) Successful in 8s
CI / Visual Tests (pull_request) Successful in 1m44s
CI / Journal Image Smoke Test (pull_request) Successful in 3m16s
CI / Checks (pull_request) Successful in 3m49s
CI / E2E Tests (pull_request) Successful in 2m55s
Cancel superseded CI / Cancel in-flight CI (pull_request) Successful in 2s
CD Staging / Tear Down PR Preview (pull_request) Successful in 15s
97b5afb2b4
#272 and #273 each added an undici@8.12.1 entry and both merged, leaving
duplicate mapping keys. pnpm treats the lockfile as broken, ignores it,
and re-resolves from scratch on every install, dirtying the tree.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ullrich deleted branch fix-duplicate-undici-lockfile 2026-10-17 10:26:25 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
trails-cool/trails!276
No description provided.