-
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
chore(deps): update all (major) #175
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-all
base: master
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.
Open
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/major-all
branch
from
October 26, 2021 02:14
703da9f
to
63bde28
Compare
renovate
bot
changed the title
chore(deps): update dependency eslint to v8
chore(deps): update all (major)
Oct 26, 2021
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
November 13, 2021 18:57
fc8026a
to
60cf322
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
January 11, 2022 10:47
60cf322
to
a1240fe
Compare
renovate
bot
changed the title
chore(deps): update all (major)
chore(deps): update node.js to v16
Jan 11, 2022
renovate
bot
force-pushed
the
renovate/major-all
branch
from
March 7, 2022 15:04
a1240fe
to
5db6ab9
Compare
renovate
bot
changed the title
chore(deps): update node.js to v16
chore(deps): update all (major)
Mar 7, 2022
renovate
bot
force-pushed
the
renovate/major-all
branch
from
April 24, 2022 19:14
5db6ab9
to
7b109bc
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 15, 2022 19:27
7b109bc
to
4a9c41c
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
June 18, 2022 17:02
4a9c41c
to
e5396a6
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
September 25, 2022 22:33
e5396a6
to
cabf33f
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
November 20, 2022 07:54
cabf33f
to
a6fc766
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
March 16, 2023 19:49
a6fc766
to
f274021
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
March 24, 2023 22:36
f274021
to
1d9752d
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
April 17, 2023 09:31
1d9752d
to
185d3ad
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
June 9, 2023 17:12
185d3ad
to
c6f2dea
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
July 5, 2023 17:12
933abfe
to
33a74f1
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
August 5, 2023 19:21
33a74f1
to
87fbbdd
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
August 17, 2023 17:15
445da16
to
4c880cb
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
August 24, 2023 16:02
4c880cb
to
96fb1b2
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
September 4, 2023 12:33
96fb1b2
to
5377506
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
September 22, 2023 20:04
5377506
to
1560099
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
October 17, 2023 17:27
b248fd8
to
b69bb02
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 23, 2023 13:55
b69bb02
to
93c05b3
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
October 24, 2023 00:39
aac6646
to
cbc955c
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
December 18, 2023 12:39
cbc955c
to
7cba0d7
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
January 25, 2024 03:56
7cba0d7
to
aa95286
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
February 7, 2024 07:29
aa95286
to
0012222
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
April 5, 2024 21:24
0012222
to
76885d6
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
April 25, 2024 15:14
86643cb
to
73988d7
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 9, 2024 02:04
73988d7
to
da1ff32
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 16, 2024 23:03
da1ff32
to
f06b0d1
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
June 12, 2024 20:09
f06b0d1
to
26b5b7a
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
July 9, 2024 16:50
d5509f4
to
5e5fd71
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
September 26, 2024 11:48
f9ebb92
to
3379200
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 7, 2024 19:12
3379200
to
7b5f683
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
October 29, 2024 02:24
8c04c78
to
15797b9
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 30, 2024 23:45
15797b9
to
915951d
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:
^17.0.8
->^22.0.0
v2.3.4
->v4.2.2
v2.4.1
->v4.1.0
^8.3.0
->^9.0.0
^7.0.4
->^9.0.0
^12.1.7
->^15.0.0
14
->22
^2.5.1
->^3.0.0
^3.0.2
->^6.0.0
^1.1.8
->^2.0.0
^4.5.4
->^5.0.0
Release Notes
actions/checkout (actions/checkout)
v4.2.2
Compare Source
url-helper.ts
now leverages well-known environment variables by @jww3 in https://github.com/actions/checkout/pull/1941isGhes
by @jww3 in https://github.com/actions/checkout/pull/1946v4.2.1
Compare Source
v4.2.0
Compare Source
v4.1.7
Compare Source
v4.1.6
Compare Source
v4.1.5
Compare Source
What's Changed
user.email
to be41898282+github-actions[bot]@​users.noreply.github.com
by @cory-miller in https://github.com/actions/checkout/pull/1707Full Changelog: actions/checkout@v4.1.4...v4.1.5
v4.1.4
Compare Source
extensions.worktreeConfig
when disablingsparse-checkout
by @jww3 in https://github.com/actions/checkout/pull/1692v4.1.3
Compare Source
What's Changed
actions/checkout
version inupdate-main-version.yml
by @jww3 in https://github.com/actions/checkout/pull/1650sparse-checkout
by @jww3 in https://github.com/actions/checkout/pull/1656Full Changelog: actions/checkout@v4.1.2...v4.1.3
v4.1.2
Compare Source
sparse-checkout
option is not present @dscho in https://github.com/actions/checkout/pull/1598v4.1.1
Compare Source
What's Changed
New Contributors
Full Changelog: actions/checkout@v4.1.0...v4.1.1
v4.1.0
Compare Source
v4.0.0
Compare Source
v3.6.0
Compare Source
v3.5.3
Compare Source
v3.5.2
Compare Source
v3.5.1
Compare Source
v3.5.0
Compare Source
v3.4.0
Compare Source
v3.3.0
Compare Source
v3.2.0
Compare Source
v3.1.0
Compare Source
saveState
andgetState
github-server-url
inputv3.0.2
Compare Source
set-safe-directory
v3.0.1
Compare Source
safe.directory
v3.0.0
Compare Source
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
actions/setup-node (actions/setup-node)
v4.1.0
Compare Source
v4.0.4
Compare Source
v4.0.3
Compare Source
v4.0.2
Compare Source
What's Changed
volta.extends
by @ThisIsManta in https://github.com/actions/setup-node/pull/921New Contributors
Full Changelog: actions/setup-node@v4.0.1...v4.0.2
v4.0.1
Compare Source
What's Changed
package.json
tonode-version-file
list of examples. by @TWiStErRob in https://github.com/actions/setup-node/pull/879New Contributors
Full Changelog: actions/setup-node@v4...v4.0.1
v4.0.0
Compare 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 https://github.com/actions/setup-node/pull/866
Besides, release contains such changes as:
New Contributors
Full Changelog: actions/setup-node@v3...v4.0.0
v3.8.2
Compare Source
What's Changed
Full Changelog: actions/setup-node@v3...v3.8.2
v3.8.1
Compare Source
What's Changed
In scope of this release, the filter was removed within the cache-save step by @dmitry-shibanov in https://github.com/actions/setup-node/pull/831. It is filtered and checked in the toolkit/cache library.
Full Changelog: actions/setup-node@v3...v3.8.1
v3.8.0
Compare 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.0
Compare 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-path
input 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 (https://github.com/actions/setup-node/pull/611) and canary (https://github.com/actions/setup-node/pull/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. https://github.com/actions/setup-node/pull/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
https://github.com/actions/setup-node/pull/545. Moreover we fixed the issue with falling on node-version output https://github.com/actions/setup-node/pull/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/cache
package as the new version contains fixes for caching error handling. Moreover, we added support for asdf format as Node.js version file https://github.com/actions/setup-node/pull/373. Besides, we introduced new output node-version and addednpm-shrinkwrap.json
to dependency file patterns: https://github.com/actions/setup-node/pull/439v3.3.0
: Add support for lts/-n aliasesCompare Source
In scope of this release we added support for
lts/-n
aliases, improve logic forcurrent
,latest
andnode
aliases to handle them fromtoolcache
, updatencc
package.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. https://github.com/actions/setup-node/pull/483
v3.1.1
: Update actions/cache version to 2.0.2Compare Source
In scope of this release we updated
actions/cache
package as the new version contains fixes related to GHES 3.5 (https://github.com/actions/setup-node/pull/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/cache
dependency to 2.0.0 version.v3.0.0
Compare 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
version
input (https://github.com/actions/setup-node/pull/424). Please usenode-version
input instead.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.
prettier/eslint-config-prettier (eslint-config-prettier)
v9.1.0
Compare Source
ESLINT_CONFIG_PRETTIER_NO_DEPRECATED
environment variable.v9.0.0
Compare Source
"unicode-bom": "off"
to your config to disable it again, or run ESLint with--fix
to fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@nstepien)!v8.10.0
Compare Source
v8.9.0
Compare Source
v8.8.0
Compare Source
v8.7.0
Compare Source
v8.6.0
Compare Source
v8.5.0
Compare Source
v8.4.0
Compare Source
typicode/husky (husky)
v9.1.6
Compare Source
v9.1.5
Compare Source
v9.1.4
Compare Source
v9.1.3
Compare Source
PATH
v9.1.2
Compare Source
v9.1.1
Compare Source
v9.1.0
Compare Source
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone Europe/Berlin, 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.