Breaking changes
The latest Yarn version will no longer be installed, instead it will be managed by Corepack.
Previously, the step always installed Yarn globally which can result in builds, that are not reproducible. This can cause issues, because the local setup and the CI environment would most likely differ and behave unexpectedly.
Instead, the step expects Yarn version to be provided by packageManager field in package.json, this way Corepack can handle the version management.
The step will not break without version pinning, but it is recommended to use the new, modern method and provide the required Yarn version.
What鈥檚 Changed
- Utilize corepack instead of yarn global install by @marcell-vida in Utilize corepack instead of yarn global install by marcell-vida 路 Pull Request #31 路 bitrise-steplib/steps-yarn 路 GitHub
New Contributors
- @marcell-vida made their first contribution in Utilize corepack instead of yarn global install by marcell-vida 路 Pull Request #31 路 bitrise-steplib/steps-yarn 路 GitHub
Full Changelog: Comparing 1.0.0...2.0.0 路 bitrise-steplib/steps-yarn 路 GitHub