aries-framework-go GitHub

Sourced from actions/setup-node's releases.

Add current, node, latest aliases

In scope of this release we added new aliases to install the latest Node.js version. actions/setup-node#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 (actions/setup-node#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

• With the update to Node 16 in actions/setup-node#414, all scripts will now be run with Node 16 rather than Node 12.
• We removed deprecated version input (actions/setup-node#424). Please use node-version input instead.

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 (actions/setup-node#358) and (actions/setup-node#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 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

... (truncated)

• 17f8bd9 Expand current syntax to support aliases for latest version (current/latest/n...
• b067f78 Use CI friendly commands in documentation (#326)
• 0bd0676 Improve advanced usage docs (#472)
• 25184c4 Update README.md (#475)
• 337fdf2 fix broken link in readme (#473)
• 86bf502 extend documentation on scope parameter (#470)
• 146c4d8 improve caching documentation (#468)
• 56337c4 Updated @​actions/cache (#460)
• 76d3665 Convert CONDUCT to CODE_OF_CONDUCT.md (#391)
• 5b52f09 Bump actions/checkout@v3 within advanced usage examples documentation (#456)
• Additional commits viewable in compare view