Configuring the packageManager viadevEngines to only allow yarn causes release-it to fail

// package.json"devEngines": {"packageManager": {"name":"yarn","onFail":"error"  }}

It will fail with a rather cryptic error message

ERROR Unable to reach npm registry (timed out after 10000ms).

The reason becomes clear when running with--dry-run

! npm ping --registry https://registry.npmjs.org! npm whoami --registry https://registry.npmjs.org

it's usingnpm to run commands and devEngines is blocking it as only yarn is allowed.

I'm not sure what the correct solution is here. The intend of devEngines is to stop accidentalnpm install in a yarn project.