chore(deps): update all non-major github action dependencies #2961
+3
−3
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
->v2.7.0
v3
->v3.6.0
v2
->v2.5.2
Review
Release Notes
actions/checkout (actions/checkout)
v2.7.0
Compare Source
What's Changed
Full Changelog: actions/checkout@v2.6.0...v2.7.0
v2.6.0
Compare Source
What's Changed
Full Changelog: actions/checkout@v2.5.0...v2.6.0
v2.5.0
Compare Source
What's Changed
Full Changelog: actions/checkout@v2...v2.5.0
v2.4.2
Compare Source
What's Changed
Full Changelog: actions/checkout@v2...v2.4.2
v2.4.1
Compare Source
safe.directory
v2.4.0
Compare Source
org-<ORG_ID>@​github.com:
tohttps://github.com/
- prv2.3.5
Compare Source
Update dependencies
v2.3.4
Compare Source
await
sv2.3.3
Compare Source
v2.3.2
Compare Source
Add Third Party License Information to Dist Files
v2.3.1
Compare Source
v2.3.0
Compare Source
v2.2.0
Compare Source
v2.1.1
Compare Source
v2.1.0
Compare Source
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
v2.1.2
: (beta)Compare Source
v2.1.1
: (beta)Compare Source
Switch to
main
branch 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: Branch creation - "every weekend" in timezone America/Montreal, 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.