You get no warning and shrinkwrap errors appear if you attempt to update a package to a later version which is being overridden by pnpm-config.json's globalOverrides feature.
Repro steps
Go to pnpm-config.json, add globalOverrides property and add an entry being setting it to current version of a package today.
Run rush update --recheck
a. You should see successful lockfile update created in git
Try to update the version of that package (in some project)
Run rush update
Expected result:
Few Expectations:
User is alerted that they are trying to update a package which is being overridden by pnpm-config.json
rush update fails (perhaps in rush check stage) with the same error
Actual result:
You get the following warning which says the shrinkwrap file contains issues:
This terminal feedback appears unclear as it looks like your build has successfully completed, however you don't have a new lockfile, and in CI your build will fail because of this error.
Summary
You get no warning and shrinkwrap errors appear if you attempt to update a package to a later version which is being overridden by
pnpm-config.json
's globalOverrides feature.Repro steps
pnpm-config.json
, addglobalOverrides
property and add an entry being setting it to current version of a package today.rush update --recheck
a. You should see successful lockfile update created in gitrush update
Expected result: Few Expectations:
pnpm-config.json
rush update
fails (perhaps inrush check
stage) with the same errorActual result: You get the following warning which says the shrinkwrap file contains issues:
This terminal feedback appears unclear as it looks like your build has successfully completed, however you don't have a new lockfile, and in CI your build will fail because of this error.