stale[bot]
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This PR contains the following updates:
v2.4.0->v2.5.1Release Notes
actions/setup-node
### [`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). ### [`v2.4.1`](https://togithub.com/actions/setup-node/releases/v2.4.1) [Compare Source](https://togithub.com/actions/setup-node/compare/v2.4.0...v2.4.1) This release introduces a new output: `cache-hit` ([#327](https://togithub.com/actions/setup-node/issues/327)). The `cache-hit` output contains boolean value indicating that an exact match was found for the key. It shows that the action uses already existing cache or not. The output is available only if cache is enabled.Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled due to failing status checks.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 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.