Issue description
We use dedicated build agents for our PR pipeline jobs so we don't clean the repo so that we save time doing npm install.
There are cases when shrinkwrap present on machine is not changed so rush skips running pnpm install command.
We had a case where common-versions.json was changed so rush skipped install and pr went thru fine. But the official build started failing because version specified in common-versions.json was not existing.
Expected Behaviour
Rush should include a way to check change in common-versions.json file also before skipping pnpm install
Extra note
This seems to be coming from here
Issue description
We use dedicated build agents for our PR pipeline jobs so we don't clean the repo so that we save time doing npm install.
There are cases when shrinkwrap present on machine is not changed so rush skips running pnpm install command.
We had a case where common-versions.json was changed so rush skipped install and pr went thru fine. But the official build started failing because version specified in common-versions.json was not existing.
Expected Behaviour
Rush should include a way to check change in common-versions.json file also before skipping pnpm install
Extra note
This seems to be coming from here