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.

Sign up for GitHub

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

Jump to bottom

Update actions/setup-node action to v4 #15

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

Update actions/setup-node action to v4 #15

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 23, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
actions/setup-node action major v2.1.2 -> v4.0.4

Release Notes

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

v4.0.4

Compare Source

v4.0.3

Compare Source

v4.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4.0.1...v4.0.2

v4.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.1

v4.0.0

Compare Source

What's Changed

In scope of this release we changed version of node runtime for action from node16 to node20 and updated dependencies in https://github.com/actions/setup-node/pull/866

Besides, release contains such changes as:

New Contributors

Full Changelog: actions/setup-node@v3...v4.0.0

v3.8.2

Compare Source

What's Changed

Full Changelog: actions/setup-node@v3...v3.8.2

v3.8.1

Compare Source

What's Changed

In scope of this release, the filter was removed within the cache-save step by @​dmitry-shibanov in https://github.com/actions/setup-node/pull/831. It is filtered and checked in the toolkit/cache library.

Full Changelog: actions/setup-node@v3...v3.8.1

v3.8.0

Compare Source

What's Changed
Bug fixes:
Feature implementations:
Documentation changes:
Update dependencies:
New Contributors

Full Changelog: actions/setup-node@v3...v3.8.0

v3.7.0

Compare Source

What's Changed

In scope of this release we added a logic to save an additional cache path for yarn 3 (related pull request and feature request). Moreover, we added functionality to use all the sub directories derived from cache-dependency-path input and add detect all dependencies directories to cache (related pull request and feature request).

Besides, we made such changes as:

New Contributors

Full Changelog: actions/setup-node@v3...v3.7.0

v3.6.0: Add Support for Nightly, Canary and RC builds for Node.js

Compare Source

In scope of this release we added support to download nightly, rc (https://github.com/actions/setup-node/pull/611) and canary (https://github.com/actions/setup-node/pull/619) Node.js distributions.

For nightly versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16-nightly'
      - run: npm ci
      - run: npm test
For canary versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16-v8-canary’
      - run: npm ci
      - run: npm test
For rc versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16.0.0-rc.1’
      - run: npm ci
      - run: npm test

Note: For more examples please refer to documentation.

Besides, we added the following changes as:

v3.5.1: Update @​actions/core and Print Node, Npm, Yarn versions

Compare Source

In scope of this release we updated actions/core to 1.10.0. Moreover, we added logic to print Nodejs, Npm, Yarn versions after installation.

v3.5.0: Add support for engines.node and Volta

Compare Source

In scope of this release we add support for engines.node. The action will be able to grab the version form package.json#engines.node. https://github.com/actions/setup-node/pull/485. Moreover, we added support for Volta

Besides, we updated @​actions/core to 1.9.1 and @​actions/cache to 3.0.4

v3.4.1: Fix pnpm output and node-version output issues

Compare Source

In scope of this release we fixed bugs related to the pnpm 7.5.1 output issue from pnpm store path https://github.com/actions/setup-node/pull/545. Moreover we fixed the issue with falling on node-version output https://github.com/actions/setup-node/pull/540.

v3.4.0: Add support for asdf format and update actions/cache version to 3.0.0

Compare Source

In scope of this release we updated actions/cache package as the new version contains fixes for caching error handling. Moreover, we added support for asdf format as Node.js version file https://github.com/actions/setup-node/pull/373. Besides, we introduced new output node-version and added npm-shrinkwrap.json to dependency file patterns: https://github.com/actions/setup-node/pull/439

v3.3.0: Add support for lts/-n aliases

Compare Source

In scope of this release we added support for lts/-n aliases, improve logic for current, latest and node aliases to handle them from toolcache, update ncc package.

Support of lts/-n aliases
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
  with:
    node-version: lts/-1
- run: npm ci
- run: npm test
Minor improvements

v3.2.0: Add current, node, latest aliases

Compare Source

In scope of this release we added new aliases to install the latest Node.js version. https://github.com/actions/setup-node/pull/483

steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
  with:
    node-version: current
- run: npm ci
- run: npm test

v3.1.1: Update actions/cache version to 2.0.2

Compare Source

In scope of this release we updated actions/cache package as the new version contains fixes related to GHES 3.5 (https://github.com/actions/setup-node/pull/460)

v3.1.0: Add caching support on GHES 3.5

Compare Source

In scope of this release we added support for caching from GHES 3.5 and fixed download issue for files > 2GB during restore. Besides, we updated actions/cache dependency to 2.0.0 version.

v3.0.0

Compare Source

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

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

  • 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 force-pushed the renovate/actions-setup-node-4.x branch from accc830 to 34ec937 Compare December 18, 2023 12:00
@renovate renovate bot force-pushed the renovate/actions-setup-node-4.x branch from 34ec937 to da903be Compare February 7, 2024 06:14
@renovate renovate bot force-pushed the renovate/actions-setup-node-4.x branch from da903be to 0d0b413 Compare July 9, 2024 15:54
@renovate renovate bot force-pushed the renovate/actions-setup-node-4.x branch from 0d0b413 to 6765057 Compare September 19, 2024 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants