fix(pnpm): disable frozen-lockfile to resolve CI lockfile mismatches#50
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Problema
pnpm v10 activa automáticamente el modo `--frozen-lockfile` cuando detecta `CI=true`. Las PRs de Renovate generan lockfiles sin la sección `overrides` (aunque `package.json` las tenga), lo que causa `ERR_PNPM_LOCKFILE_CONFIG_MISMATCH` en todas las PRs de actualización de dependencias.
Solución
Añadir `.npmrc` con `frozen-lockfile=false` para que `pnpm install` pueda regenerar y corregir el lockfile automáticamente durante el CI, sin necesidad de modificar el workflow (que requiere el scope `workflow` del token).
Efecto
Una vez mergeada, Renovate hará rebase de todas las PRs fallidas y el CI pasará correctamente.