Breaking changes
The way the right NPM version is installed has changed slightly.
Previously, the step read your package.json and its engines field to see if a specific NPM version is declared. Since the engines field can contain version ranges and other ambiguous version constraints (see #54), this is not a reliable way to install the right NPM version in CI.
Instead, the step looks at the packageManager field in package.json, just like Corepack does. If an NPM version is declared there, the step installs that version via Corepack before executing the actual task.
The step input npm_version is still available and has higher priority than the package.json file. If no npm_version input is set and package.json has no packageManager field (or declares a different package manager than NPM), then the system-wide npm executable is used, just like in prior versions.
What鈥檚 Changed
- Rework NPM version selection by @ofalvai in Rework NPM version selection by ofalvai 路 Pull Request #60 路 bitrise-steplib/steps-npm 路 GitHub
Full Changelog: Comparing 2.0.0...3.0.0 路 bitrise-steplib/steps-npm 路 GitHub