Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update actions/setup-node action to v2.5.2 #83

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 17, 2020

This PR contains the following updates:

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

Release Notes

actions/setup-node (actions/setup-node)

v2.5.2: Update @​actions/core for v2

Compare Source

In scope of this release we updated actions/core to 1.10.0 and actions/tool-cache to 1.7.2 for v2: https://github.com/actions/setup-node/pull/713

v2.5.1: Fix logic of error handling for npm warning and uncaught exception

Compare Source

In scope of this release we fix logic of error handling related to caching (https://github.com/actions/setup-node/pull/358) and (https://github.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: Adding Node.js version file support

Compare Source

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 and values with v prefix (v14)
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.

v2.4.1: Add "cache-hit" output

Compare Source

This release introduces a new output: cache-hit (#​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: Support caching for mono repos and repositories with complex structure

Compare Source

This release introduces dependency caching support for mono repos and repositories with complex structure (#​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:

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 guide.

v2.3.2: Revert temporary fix

Compare Source

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: Temporary maintenance fix.

Compare Source

Temporarily disabled usage of pre-cached Node.js.

v2.3.0: Support caching pnpm dependencies

Compare Source

This release introduces dependency caching support for the pnpm package manager (#​278).

Caching pnpm dependencies:

### 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: Support caching dependencies and LTS aliases

Compare Source

This release brings two major features:

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:

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:

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: Release

Compare Source

Improve error and warning line number handling (problem matcher regex)

v2.1.4

Compare Source

The first stable release of actions/setup-node V2

v2.1.3: (beta)

Compare Source

  • Add support for specifying architecture of Node.JS

Configuration

📅 Schedule: Branch creation - "on friday" in timezone Australia/Melbourne, Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 17, 2020
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 3 times, most recently from 51f6ac0 to 43f4ecd Compare December 24, 2020 15:41
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from 43f4ecd to cf6d413 Compare December 31, 2020 14:28
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from cf6d413 to 6918435 Compare January 7, 2021 14:58
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 2 times, most recently from 7f25b79 to 582a9b6 Compare January 21, 2021 15:25
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 2 times, most recently from 7d12e71 to 56b9e02 Compare February 4, 2021 14:42
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 5 times, most recently from 8016881 to c1297c4 Compare February 12, 2021 06:25
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from c1297c4 to cef7405 Compare February 22, 2021 16:26
@renovate renovate bot changed the title Update actions/setup-node action to v2.1.4 Update actions/setup-node action to v2.1.5 Feb 22, 2021
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 4 times, most recently from 2c392fb to 316bcc6 Compare March 4, 2021 14:30
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 3 times, most recently from 18cc190 to d13fca2 Compare March 11, 2021 17:42
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 4 times, most recently from e9967f9 to cf99884 Compare March 18, 2021 22:28
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 2 times, most recently from c127ec9 to 73a2a98 Compare March 26, 2021 03:56
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 2 times, most recently from 811ed7b to aa0b475 Compare August 3, 2021 16:42
@renovate renovate bot changed the title Update actions/setup-node action to v2.3.0 Update actions/setup-node action to v2.3.1 Aug 3, 2021
@renovate renovate bot changed the title Update actions/setup-node action to v2.3.1 Update actions/setup-node action to v2.3.2 Aug 4, 2021
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from aa0b475 to 08dee79 Compare August 4, 2021 15:13
@renovate renovate bot changed the title Update actions/setup-node action to v2.3.2 Update actions/setup-node action to v2.4.0 Aug 5, 2021
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from 08dee79 to a396089 Compare August 5, 2021 16:59
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from a396089 to bee5060 Compare August 27, 2021 01:09
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from bee5060 to f359e08 Compare September 9, 2021 15:46
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 2 times, most recently from 69862e9 to 4c64a78 Compare September 16, 2021 16:41
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from 4c64a78 to ee75390 Compare September 27, 2021 15:07
@renovate renovate bot changed the title Update actions/setup-node action to v2.4.0 Update actions/setup-node action to v2.4.1 Sep 27, 2021
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from ee75390 to b53e8d5 Compare October 14, 2021 15:10
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from b53e8d5 to b60b8cc Compare November 4, 2021 21:17
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from b60b8cc to cd8a165 Compare November 18, 2021 15:52
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 2 times, most recently from b1089de to 06f75df Compare November 29, 2021 13:40
@renovate renovate bot changed the title Update actions/setup-node action to v2.4.1 Update actions/setup-node action to v2.5.0 Nov 29, 2021
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 2 times, most recently from 69884fc to fa72efa Compare December 10, 2021 00:37
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from fa72efa to a811841 Compare December 16, 2021 16:49
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from a811841 to 9a246dc Compare December 28, 2021 11:12
@renovate renovate bot changed the title Update actions/setup-node action to v2.5.0 Update actions/setup-node action to v2.5.1 Dec 28, 2021
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch 3 times, most recently from 10a81da to 598578b Compare June 23, 2022 19:11
@renovate renovate bot changed the title Update actions/setup-node action to v2.5.1 Update actions/setup-node action to v2.5.2 Mar 27, 2023
@renovate renovate bot force-pushed the renovate/actions-setup-node-2.x branch from 598578b to 4ae8f52 Compare March 27, 2023 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants