Skip to content

lockfile fix and changes#356

Merged
codingfrog27 merged 1 commit intomainfrom
lockfile-fix-and-future-proving
Feb 17, 2026
Merged

lockfile fix and changes#356
codingfrog27 merged 1 commit intomainfrom
lockfile-fix-and-future-proving

Conversation

@codingfrog27
Copy link
Contributor

Looked into lockfile issues again and how to prevent them.

Findings

  • The issue was not only out of sync lockfiles being pushed. But the Pnpm version used in the Github CI being outdated. (8 instead of 10)
  • Pnpm 8 generates lockfile v6 and cant parse the v9 version the pnpm generates. Thus will instead generate it's own and not properly compare the push lockfile

Fixes

  • Updated CI to pnpm v10 (deploy.yml, lint.yml)
  • Added --frozen-lockfile flag to all CI install commands. Will now error on version mismatches instead of only warning
  • Regenerated lockfile with v9.0 format. Should now be in line with dependency updates again

local enforcement

Also I Created a .npmrc with frozen-lockfile=true to enforce version matching when building locally as well. This will hopefully catch version mismatches even before a PR. Noting this change since there is a risk of it being too strict/cumbersome during development.

It also has auto-install-peers=true added. This was already happening, so thought it'd be better to have it explicit

@codingfrog27 codingfrog27 merged commit 319050d into main Feb 17, 2026
10 checks passed
@codingfrog27 codingfrog27 deleted the lockfile-fix-and-future-proving branch February 17, 2026 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants