arvinxx / gitmoji-commit-workflow

😉 Gitmoji Commit Workflow
MIT License
221 stars 27 forks source link

chore(deps): update actions/setup-node action to v2.5.1 #379

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 2 years ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
actions/setup-node action minor v2.1.2 -> v2.5.1

Release Notes

actions/setup-node ### [`v2.5.1`](https://togithub.com/actions/setup-node/releases/tag/v2.5.1): Fix logic of error handling for npm warning and uncaught exception [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/tag/v2.5.0): Adding Node.js version file support [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/tag/v2.4.1): Add "cache-hit" output [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. ### [`v2.4.0`](https://togithub.com/actions/setup-node/releases/tag/v2.4.0): Support caching for mono repos and repositories with complex structure [Compare Source](https://togithub.com/actions/setup-node/compare/v2.3.2...v2.4.0) This release introduces dependency caching support for mono repos and repositories with complex structure ([#​305](https://togithub.com/actions/setup-node/issues/305)). By default, the action searches for the dependency file (`package-lock.json` or `yarn.lock`) in the repository root. Use the `cache-dependency-path` input for cases when multiple dependency files are used, or they are located in different subdirectories. This input supports wildcards or a list of file names for caching multiple dependencies. Yaml example: ```yml steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: 14 cache: npm cache-dependency-path: 'sub-project/package-lock.json' ``` For more examples of using `cache-dependency-path` input, see the [Advanced usage](https://togithub.com/actions/setup-node/blob/25316bbc1f10ac9d8798711f44914b1cf3c4e954/docs/advanced-usage.md#caching-packages-dependencies) guide. ### [`v2.3.2`](https://togithub.com/actions/setup-node/releases/tag/v2.3.2): Revert temporary fix [Compare Source](https://togithub.com/actions/setup-node/compare/v2.3.1...v2.3.2) We had to disable pre-cached Node.js usage in the previous version due to the broken image cache. Now cache is fixed, so we can safely enable its usage again. Thank you for understanding. ### [`v2.3.1`](https://togithub.com/actions/setup-node/releases/tag/v2.3.1): Temporary maintenance fix. [Compare Source](https://togithub.com/actions/setup-node/compare/v2.3.0...v2.3.1) Temporarily disabled usage of pre-cached Node.js. ### [`v2.3.0`](https://togithub.com/actions/setup-node/releases/tag/v2.3.0): Support caching pnpm dependencies [Compare Source](https://togithub.com/actions/setup-node/compare/v2.2.0...v2.3.0) This release introduces dependency caching support for the `pnpm` package manager ([#​278](https://togithub.com/actions/setup-node/issues/278)). **Caching pnpm dependencies:** ```yaml ### This workflow uses actions that are not certified by GitHub. ### They are provided by a third-party and are governed by ### separate terms of service, privacy policy, and support ### documentation. steps: - uses: actions/checkout@v2 - uses: pnpm/action-setup@646cdf48217256a3d0b80361c5a50727664284f2 with: version: 6.10.0 - uses: actions/setup-node@v2 with: node-version: '14' cache: 'pnpm' - run: pnpm install - run: pnpm test ``` **NOTE**: pnpm caching support requires pnpm version >= 6.10.0 ### [`v2.2.0`](https://togithub.com/actions/setup-node/releases/tag/v2.2.0): Support caching dependencies and LTS aliases [Compare Source](https://togithub.com/actions/setup-node/compare/v2.1.5...v2.2.0) This release brings two major features: - [Support LTS aliases #​270](https://togithub.com/actions/setup-node/pull/270) - [Implementation of node's caching #​272](https://togithub.com/actions/setup-node/pull/272) ##### Supported version syntax The `node-version` input supports the following syntax: major versions: `12`, `14`, `16`\ more specific versions: `10.15`, `14.2.0`, `16.3.0`\ nvm LTS syntax: `lts/erbium`, `lts/fermium`, `lts/*` ##### Caching dependencies The action has a built-in functionality for caching and restoring npm/yarn dependencies. Supported package managers are `npm`, `yarn`. The `cache` input is optional, and caching is turned off by default. **Caching npm dependencies:** ```yaml steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: '14' cache: 'npm' - run: npm install - run: npm test ``` **Caching yarn dependencies:** ```yaml steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: '14' cache: 'yarn' - run: yarn install - run: yarn test ``` Yarn caching handles both yarn versions: 1 or 2. > At the moment, only `lock` files in the project root are supported. ### [`v2.1.5`](https://togithub.com/actions/setup-node/releases/tag/v2.1.5): Release [Compare Source](https://togithub.com/actions/setup-node/compare/v2.1.4...v2.1.5) Improve error and warning line number handling (problem matcher regex) ### [`v2.1.4`](https://togithub.com/actions/setup-node/releases/tag/v2.1.4) [Compare Source](https://togithub.com/actions/setup-node/compare/v2.1.3...v2.1.4) The first stable release of actions/setup-node V2 ### [`v2.1.3`](https://togithub.com/actions/setup-node/releases/tag/v2.1.3): (beta) [Compare Source](https://togithub.com/actions/setup-node/compare/v2.1.2...v2.1.3) - Add support for specifying architecture of Node.JS

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 Mend Renovate. View repository job log here.

codecov[bot] commented 2 years ago

Codecov Report

Merging #379 (ca33840) into master (b302268) will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #379   +/-   ##
=======================================
  Coverage   84.45%   84.45%           
=======================================
  Files          16       16           
  Lines         148      148           
  Branches       53       53           
=======================================
  Hits          125      125           
  Misses         22       22           
  Partials        1        1           

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update b302268...ca33840. Read the comment docs.