Releases: actions/setup-node
Add support for engines.node and Volta
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. #485. Moreover, we added support for Volta
Besides, we updated @actions/core to 1.9.1 and @actions/cache to 3.0.4
Fix pnpm output and node-version output issues
Add support for asdf format and update actions/cache version to 3.0.0
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 #373. Besides, we introduced new output node-version and added npm-shrinkwrap.json
to dependency file patterns: #439
Add support for lts/-n aliases
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
Add current, node, latest aliases
In scope of this release we added new aliases to install the latest Node.js version. #483
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: current
- run: npm ci
- run: npm test
Update actions/cache version to 2.0.2
In scope of this release we updated actions/cache
package as the new version contains fixes related to GHES 3.5 (#460)
Add caching support on GHES 3.5
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
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
Fix logic of error handling for npm warning and uncaught exception
In scope of this release we fix logic of error handling related to caching (#358) and (#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.
Adding Node.js version file support
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
andnode-version-file
inputs, the action will use value from thenode-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.