actions/setup-node
### [`v2.4.0`](https://togithub.com/actions/setup-node/releases/v2.4.0)
[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/v2.3.2)
[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/v2.3.1)
[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/v2.3.0)
[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/v2.2.0)
[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/v2.1.5)
[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/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/v2.1.3)
[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: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
[ ] If you want to rebase/retry this PR, check this box.
This PR contains the following updates:
v2.1.2->v2.4.0Release Notes
actions/setup-node
### [`v2.4.0`](https://togithub.com/actions/setup-node/releases/v2.4.0) [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/v2.3.2) [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/v2.3.1) [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/v2.3.0) [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/v2.2.0) [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/v2.1.5) [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/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/v2.1.3) [Compare Source](https://togithub.com/actions/setup-node/compare/v2.1.2...v2.1.3) - Add support for specifying architecture of Node.JSConfiguration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.