You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add architecture to cache key by @pengx17 in #843
This addresses issues with caching by adding the architecture (arch) to the cache key, ensuring that cache keys are accurate to prevent conflicts.
Note: This change may break previous cache keys as they will no longer be compatible with the new format.
Upgrade @actions/cache to 4.0.3 by @gowridurgad in #1270
In scope of this release we updated actions/cache package to ensure continued support and compatibility, as older versions of the package are now deprecated. For more information please refer to the toolkit/cache.
In scope of this release, the filter was removed within the cache-save step by @dmitry-shibanov in #831. It is filtered and checked in the toolkit/cache library.
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:
Replace workflow badge with new badge by @jongwooo in #653
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
In scope of this release we fixed bugs related to the pnpm 7.5.1 output issue from pnpm store path#545. Moreover we fixed the issue with falling on node-version output #540.
v3.4.0: 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
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.
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.
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.
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 fileuses: actions/setup-node@v2with:
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.
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
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.
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.
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@646cdf48217256a3d0b80361c5a50727664284f2with:
version: 6.10.0
- uses: actions/setup-node@v2with:
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
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.
Added check-latest input option to query the versions manifest for latest version before checking for semver match in local VM cache first (the default). That's useful for ensuring you get latest as soon as it's released to the cache but at the cost of perf / reliability (much more likely to incur and download and extract).
Configuration
📅 Schedule: (UTC)
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
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
[email protected].
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/[email protected]. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2→v4Release Notes
actions/setup-node (actions/setup-node)
v4.4.0Compare Source
What's Changed
Bug fixes:
Enhancement:
Dependency update:
New Contributors
Full Changelog: actions/setup-node@v4...v4.4.0
v4.3.0Compare Source
What's Changed
Dependency updates
New Contributors
Full Changelog: actions/setup-node@v4...v4.3.0
v4.2.0Compare Source
What's Changed
@actions/cacheto^4.0.0by @priyagupta108 in #1191New Contributors
Full Changelog: actions/setup-node@v4...v4.2.0
v4.1.0Compare Source
What's Changed
isGheslogic by @jww3 in #1148This addresses issues with caching by adding the architecture (arch) to the cache key, ensuring that cache keys are accurate to prevent conflicts.
Note: This change may break previous cache keys as they will no longer be compatible with the new format.
New Contributors
Full Changelog: actions/setup-node@v4...v4.1.0
v4.0.4Compare Source
What's Changed
Documentation changes:
New Contributors
Full Changelog: actions/setup-node@v4...v4.0.4
v4.0.3Compare Source
What's Changed
Bug fixes:
Documentation changes:
Dependency updates:
New Contributors
Full Changelog: actions/setup-node@v4...v4.0.3
v4.0.2Compare Source
What's Changed
volta.extendsby @ThisIsManta in #921New Contributors
Full Changelog: actions/setup-node@v4.0.1...v4.0.2
v4.0.1Compare Source
What's Changed
package.jsontonode-version-filelist of examples. by @TWiStErRob in #879New Contributors
Full Changelog: actions/setup-node@v4...v4.0.1
v4.0.0Compare 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 #866
Besides, release contains such changes as:
New Contributors
Full Changelog: actions/setup-node@v3...v4.0.0
v4Compare Source
v3.9.1Compare Source
What's Changed
Full Changelog: actions/setup-node@v3...v3.9.1
v3.9.0Compare Source
What's Changed
In scope of this release we updated actions/cache package to ensure continued support and compatibility, as older versions of the package are now deprecated. For more information please refer to the toolkit/cache.
Full Changelog: actions/setup-node@v3...v3.9.0
v3.8.2Compare Source
What's Changed
Full Changelog: actions/setup-node@v3...v3.8.2
v3.8.1Compare Source
What's Changed
In scope of this release, the filter was removed within the cache-save step by @dmitry-shibanov in #831. It is filtered and checked in the toolkit/cache library.
Full Changelog: actions/setup-node@v3...v3.8.1
v3.8.0Compare 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.0Compare 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-pathinput 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.jsCompare Source
In scope of this release we added support to download nightly, rc (#611) and canary (#619) Node.js distributions.
For nightly versions:
For canary versions:
For rc versions:
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 versionsCompare 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 VoltaCompare 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. #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 issuesCompare Source
In scope of this release we fixed bugs related to the pnpm 7.5.1 output issue from
pnpm store path#545. Moreover we fixed the issue with falling on node-version output #540.v3.4.0: Add support for asdf format and update actions/cache version to 3.0.0Compare Source
In scope of this release we updated
actions/cachepackage 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 addednpm-shrinkwrap.jsonto dependency file patterns: #439v3.3.0: Add support for lts/-n aliasesCompare Source
In scope of this release we added support for
lts/-naliases, improve logic forcurrent,latestandnodealiases to handle them fromtoolcache, updatenccpackage.Support of lts/-n aliases
Minor improvements
v3.2.0: Add current, node, latest aliasesCompare Source
In scope of this release we added new aliases to install the latest Node.js version. #483
v3.1.1: Update actions/cache version to 2.0.2Compare Source
In scope of this release we updated
actions/cachepackage as the new version contains fixes related to GHES 3.5 (#460)v3.1.0: Add caching support on GHES 3.5Compare 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/cachedependency to 2.0.0 version.v3.0.0Compare 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
versioninput (#424). Please usenode-versioninput instead.v3Compare Source
v2.5.2: Update @actions/core for v2Compare Source
In scope of this release we updated actions/core to 1.10.0 and actions/tool-cache to 1.7.2 for v2: #713
v2.5.1: Fix logic of error handling for npm warning and uncaught exceptionCompare Source
In scope of this release we fix logic of error handling related to caching (#358) and (#359).
In the previous behaviour we relied on
stderroutput 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 supportCompare Source
In scope of this release we add the
node-version-fileinput and updateactions/cachedependency 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:node-versionandnode-version-fileinputs, the action will use value from thenode-versioninput and throw the following warning:Both node-version and node-version-file inputs are specified, only node-version will be used.vprefix (v14)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" outputCompare Source
This release introduces a new output:
cache-hit(#327).The
cache-hitoutput 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 structureCompare 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.jsonoryarn.lock) in the repository root. Use thecache-dependency-pathinput 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:
For more examples of using
cache-dependency-pathinput, see the Advanced usage guide.v2.3.2: Revert temporary fixCompare 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 dependenciesCompare Source
This release introduces dependency caching support for the
pnpmpackage manager (#278).Caching pnpm dependencies:
NOTE: pnpm caching support requires pnpm version >= 6.10.0
v2.2.0: Support caching dependencies and LTS aliasesCompare Source
This release brings two major features:
Supported version syntax
The
node-versioninput supports the following syntax:major versions:
12,14,16more specific versions:
10.15,14.2.0,16.3.0nvm 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. Thecacheinput is optional, and caching is turned off by default.Caching npm dependencies:
Caching yarn dependencies:
Yarn caching handles both yarn versions: 1 or 2.
v2.1.5: ReleaseCompare Source
Improve error and warning line number handling (problem matcher regex)
v2.1.4Compare Source
The first stable release of actions/setup-node V2
v2.1.3: (beta)Compare Source
v2.1.2: (beta)Compare Source
v2.1.1: (beta)Compare Source
Switch to
mainbranch of node-versions repository to consume latest added versions.v2.1.0: (beta)Compare Source
Added check-latest input option to query the versions manifest for latest version before checking for semver match in local VM cache first (the default). That's useful for ensuring you get latest as soon as it's released to the cache but at the cost of perf / reliability (much more likely to incur and download and extract).
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate using a curated preset maintained by