[Bug?]: yarn up does not update dependencies
Opened this issue · 2 comments
juffalow commented
Self-service
- I'd be willing to implement a fix
Describe the bug
Running yarn up
is just pretending to do something but results in no updates at all - files install-state.gz
and yarn.lock
are not modified.
To reproduce
yarn set version berry
yarn up
Environment
System:
OS: Linux 6.6 Alpine Linux
CPU: (8) arm64 unknown
Binaries:
Node: 20.14.0 - /tmp/xfs-bf9a4f20/node
Yarn: 4.4.0 - /tmp/xfs-bf9a4f20/yarn
npm: 10.7.0 - /usr/local/bin/npm
Additional context
Output from yarn up
:
➤ YN0000: · Yarn 4.4.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 221ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ typescript is listed by your project with version 5.4.5 (pfe292), which doesn't satisfy what react-scripts and other dependencies request (^3.2.1 || ^3.2.1 || ^3.3.0-dev || ^3.4.0-dev || ^3.5.0-dev || ^3.6.0-dev || ^3.6.0-beta || ^3.7.0-dev || ^3.7.0-beta || ^4.0.0 || ^4.0.0 || ^4.0.0 || ^4.0.0 || ^4.0.0 || ^4.0.0 || ^4.0.0 || ^4.0.0 || ^4.0.0).
➤ YN0002: │ frontend@workspace:. doesn't provide @popperjs/core (pa3f4a), requested by bootstrap.
➤ YN0002: │ frontend@workspace:. doesn't provide @testing-library/dom (p5a470), requested by @testing-library/user-event.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 620ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 846ms
➤ YN0000: · Done with warnings in 1s 760ms
o-l-a-v commented
I've also noticed that if I delete yarn.lock
the one getting created with yarn install
includes a huge amount of changes, as in
updates. I have a repo with Docusaurus where GitHub dependabot/security complains about webpack < 5.94.0. yarn upgrade-interactive
and yarn up
did not fix it. Deleting yarn.lock
then yarn install
, and suddenly I had webpack v5.94.0 instead.
Don't know if this is related to this issue. But thought I'd comment it here rather than creating a new issue.
Yarn v4.4.1 using fnm + NodeJS v20.17.0 + Corepack.