-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Update actions/setup-node action to v2.5.2 #83
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/actions-setup-node-2.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
3 times, most recently
from
December 24, 2020 15:41
51f6ac0
to
43f4ecd
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
December 31, 2020 14:28
43f4ecd
to
cf6d413
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
January 7, 2021 14:58
cf6d413
to
6918435
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
2 times, most recently
from
January 21, 2021 15:25
7f25b79
to
582a9b6
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
2 times, most recently
from
February 4, 2021 14:42
7d12e71
to
56b9e02
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
5 times, most recently
from
February 12, 2021 06:25
8016881
to
c1297c4
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
February 22, 2021 16:26
c1297c4
to
cef7405
Compare
renovate
bot
changed the title
Update actions/setup-node action to v2.1.4
Update actions/setup-node action to v2.1.5
Feb 22, 2021
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
4 times, most recently
from
March 4, 2021 14:30
2c392fb
to
316bcc6
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
3 times, most recently
from
March 11, 2021 17:42
18cc190
to
d13fca2
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
4 times, most recently
from
March 18, 2021 22:28
e9967f9
to
cf99884
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
2 times, most recently
from
March 26, 2021 03:56
c127ec9
to
73a2a98
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
2 times, most recently
from
August 3, 2021 16:42
811ed7b
to
aa0b475
Compare
renovate
bot
changed the title
Update actions/setup-node action to v2.3.0
Update actions/setup-node action to v2.3.1
Aug 3, 2021
renovate
bot
changed the title
Update actions/setup-node action to v2.3.1
Update actions/setup-node action to v2.3.2
Aug 4, 2021
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
August 4, 2021 15:13
aa0b475
to
08dee79
Compare
renovate
bot
changed the title
Update actions/setup-node action to v2.3.2
Update actions/setup-node action to v2.4.0
Aug 5, 2021
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
August 5, 2021 16:59
08dee79
to
a396089
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
August 27, 2021 01:09
a396089
to
bee5060
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
September 9, 2021 15:46
bee5060
to
f359e08
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
2 times, most recently
from
September 16, 2021 16:41
69862e9
to
4c64a78
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
September 27, 2021 15:07
4c64a78
to
ee75390
Compare
renovate
bot
changed the title
Update actions/setup-node action to v2.4.0
Update actions/setup-node action to v2.4.1
Sep 27, 2021
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
October 14, 2021 15:10
ee75390
to
b53e8d5
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
November 4, 2021 21:17
b53e8d5
to
b60b8cc
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
November 18, 2021 15:52
b60b8cc
to
cd8a165
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
2 times, most recently
from
November 29, 2021 13:40
b1089de
to
06f75df
Compare
renovate
bot
changed the title
Update actions/setup-node action to v2.4.1
Update actions/setup-node action to v2.5.0
Nov 29, 2021
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
2 times, most recently
from
December 10, 2021 00:37
69884fc
to
fa72efa
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
December 16, 2021 16:49
fa72efa
to
a811841
Compare
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
December 28, 2021 11:12
a811841
to
9a246dc
Compare
renovate
bot
changed the title
Update actions/setup-node action to v2.5.0
Update actions/setup-node action to v2.5.1
Dec 28, 2021
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
3 times, most recently
from
June 23, 2022 19:11
10a81da
to
598578b
Compare
renovate
bot
changed the title
Update actions/setup-node action to v2.5.1
Update actions/setup-node action to v2.5.2
Mar 27, 2023
renovate
bot
force-pushed
the
renovate/actions-setup-node-2.x
branch
from
March 27, 2023 21:46
598578b
to
4ae8f52
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.1.2
->v2.5.2
Release Notes
actions/setup-node (actions/setup-node)
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: https://github.com/actions/setup-node/pull/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 (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 supportCompare Source
In scope of this release we add the
node-version-file
input and updateactions/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: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
.v
prefix (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-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 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.json
oryarn.lock
) in the repository root. Use thecache-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:
For more examples of using
cache-dependency-path
input, 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
pnpm
package 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-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
. Thecache
input 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.4
Compare Source
The first stable release of actions/setup-node V2
v2.1.3
: (beta)Compare Source
Configuration
📅 Schedule: Branch creation - "on friday" in timezone Australia/Melbourne, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.