vercel[bot]
commented
2 years ago This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/mause/financial-dash/4xWopfae27fGzB6j9UCcukECKPBs
✅ Preview: https://financial-dash-git-renovate-actions-setup-node-3x-mause.vercel.app
This PR contains the following updates:
v2.4.1->v3.0.0Release Notes
actions/setup-node
### [`v3.0.0`](https://togithub.com/actions/setup-node/releases/v3.0.0) [Compare Source](https://togithub.com/actions/setup-node/compare/v2.5.1...v3.0.0) In scope of this release we changed version of the runtime Node.js for the setup-node action and updated package-lock.json file to v2. ##### Breaking Changes - With the update to Node 16 in [https://github.com/actions/setup-node/pull/414](https://togithub.com/actions/setup-node/pull/414), all scripts will now be run with Node 16 rather than Node 12. - We removed deprecated `version` input ([https://github.com/actions/setup-node/pull/424](https://togithub.com/actions/setup-node/pull/424)). Please use `node-version` input instead. ### [`v2.5.1`](https://togithub.com/actions/setup-node/releases/v2.5.1) [Compare Source](https://togithub.com/actions/setup-node/compare/v2.5.0...v2.5.1) In scope of this release we fix logic of error handling related to caching ([https://github.com/actions/setup-node/pull/358](https://togithub.com/actions/setup-node/pull/358)) and ([https://github.com/actions/setup-node/pull/359](https://togithub.com/actions/setup-node/pull/359)). In the previous behaviour we relied on `stderr` output to throw error. The warning messages from package managers can be written to the stderr's output. For now the action will throw an error only if exit code differs from zero. Besides, we add logic to сatch and log unhandled exceptions. ### [`v2.5.0`](https://togithub.com/actions/setup-node/releases/v2.5.0) [Compare Source](https://togithub.com/actions/setup-node/compare/v2.4.1...v2.5.0) In scope of this release we add the `node-version-file` input and update `actions/cache` dependency to the latest version. ##### Adding Node.js version file support The new input (`node-version-file`) provides functionality to specify the path to the file containing Node.js's version with such behaviour: - If the file does not exist the action will throw an error. - If you specify both `node-version` and `node-version-file` inputs, the action will use value from the `node-version` input and throw the following warning: `Both node-version and node-version-file inputs are specified, only node-version will be used`. - For now the action does not support all of the variety of values for Node.js version files. The action can handle values according to the [documentation](https://togithub.com/actions/setup-node#supported-version-syntax) and values with `v` prefix (`v14`) ```yaml steps: - uses: actions/checkout@v2 - name: Setup node from node version file uses: actions/setup-node@v2 with: node-version-file: '.nvmrc' - run: npm install - run: npm test ``` ##### Update actions/cache dependency to 1.0.8 version. We updated actions/cache dependency to the latest version (1.0.8). For more information please refer to the [toolkit/cache](https://togithub.com/actions/toolkit/blob/main/packages/cache/RELEASES.md).Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.