[Bug?]: If yarn v4 runs scripts with yarn self, it will fallback to 1.22.22

[asika32764]

Self-service

• I'd be willing to implement a fix

Describe the bug

The package.json file:

{
  "name": "app",
  "private": true,
  "type": "module",
  "scripts": {
    ...
    "deploy": "git pull && yarn install && yarn build-only"
  },
  ...
  "packageManager": "[email protected]"
}

When running yarn install, it correctly shows 4.6.0

$ yarn install

➤ · Yarn 4.6.0
➤ ┌ Resolution step
➤ └ Completed
...

But if I run yarn deploy, it shows 1.2.22 when running the yarn install sub command:

$ yarn deploy

Already up to date.
yarn install v1.22.22
[1/4] 🔍  Resolving packages...

I can make sure I didn't install yarn 1.2.22 before, see npm list:

$ npm list -g
/.../.nvm/versions/node/v22.13.1/lib
├── @ionic/[email protected]
├── [email protected]
└── [email protected]

To reproduce

As the description.

Environment

System:
    OS: macOS 14.3.1
    CPU: (12) arm64 Apple M3 Pro
  Binaries:
    Node: 22.13.1 - /private/var/folders/sj/yrz5w0ys3cxf73d50l60v39w0000gn/T/xfs-c80f26e4/node
    Yarn: 4.6.0 - /private/var/folders/sj/yrz5w0ys3cxf73d50l60v39w0000gn/T/xfs-c80f26e4/yarn
    npm: 11.1.0 - /Applications/ServBay/script/alias/npm

----

  System:
    OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (1) x64 AMD EPYC 7713 64-Core Processor
  Binaries:
    Node: 20.17.0 - /tmp/xfs-a72f763d/node
    Yarn: 4.6.0 - /tmp/xfs-a72f763d/yarn
    npm: 10.8.2 - /usr/bin/npm

Additional context

No response

[asika32764]

The reason is that I was added yarn as dependencies, it works correctly after I remove it.

Close this issue.