fix(deps): sync the lockfile with eslint-config 29.0.1 - #1119
Conversation
The 29.0.1 release repointed lint-staged-config's manifest without regenerating pnpm-lock.yaml, which still records 29.0.0, so every job on main dies at `pnpm install --frozen-lockfile`. This also deadlocks the release pipeline. `Semantic Release` starts with a "Wait for tests to succeed" gate, the tests cannot pass while the lockfile is stale, and the lockfile is only refreshed from inside that same job — so the pipeline cannot repair itself and stays blocked until a lockfile lands by hand. This is the second occurrence today; 29.0.0 needed the same fix in #1118. Regenerate. Verified with the same frozen install CI runs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014FP75FgnREe4L45kZtsa9a
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Thank you for following the naming conventions! 🙏 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
mainis red and the release pipeline is deadlocked.Symptom
Every job on
maindies at install:The 29.0.1 release repointed
lint-staged-config's manifest but left the lockfile recording 29.0.0.Why it cannot self-heal
semantic-release.ymlopens with a "Wait for tests to succeed" gate requiring every other check to pass. The lockfile is only refreshed from inside that same job. So:Semantic Releaseblocks at the gate and never reaches the refresh stepmainstays red until a lockfile is committed by handThis is the second occurrence today — 29.0.0 needed the identical fix in #1118 — so it is a recurring property of the release process, not a one-off.
This PR
Regenerates the lockfile. Verified with
pnpm install --frozen-lockfile --prefer-offline(exit 0), then build 8/8, lint 6/6, tests 4/4 projects.Worth fixing properly
This will recur on the next release that bumps a cross-package dependency. Options, roughly in order of preference:
pnpm-lock.yamlin the same commit that bumps dependents' manifests, so the two never diverge.Happy to follow up with whichever direction you prefer.
🤖 Generated with Claude Code
https://claude.ai/code/session_014FP75FgnREe4L45kZtsa9a