generated from john-d-pelingo/node-typescript-template
-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix(deps): update all (major) #226
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 10, 2021 10:46
40438bb
to
a883016
Compare
renovate
bot
changed the title
chore(deps): update dependency eslint to v8
chore(deps): update all (major)
Oct 10, 2021
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 26, 2021 01:19
a883016
to
5c5f698
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
November 13, 2021 20:24
ab91786
to
f623e21
Compare
renovate
bot
changed the title
chore(deps): update all (major)
chore(deps): update node.js to v16
Dec 11, 2021
renovate
bot
force-pushed
the
renovate/major-all
branch
from
December 12, 2021 00:27
f623e21
to
3dcee94
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
January 24, 2022 13:25
3dcee94
to
db90e51
Compare
renovate
bot
changed the title
chore(deps): update node.js to v16
chore(deps): update all (major)
Jan 24, 2022
renovate
bot
force-pushed
the
renovate/major-all
branch
from
March 7, 2022 15:57
db90e51
to
39323a2
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
April 25, 2022 02:03
39323a2
to
cd07692
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 15, 2022 23:10
cd07692
to
a710b23
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
June 18, 2022 20:11
a710b23
to
a3878e8
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
September 25, 2022 11:33
a3878e8
to
020e654
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
March 16, 2023 13:30
020e654
to
e18ce40
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
March 24, 2023 20:15
e18ce40
to
d17feb5
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
April 17, 2023 12:36
d17feb5
to
25e5740
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 28, 2023 11:00
25e5740
to
ed4d033
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
June 14, 2023 02:09
ed4d033
to
b16f54f
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
July 5, 2023 14:48
b16f54f
to
2c6eeb9
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
August 5, 2023 21:39
2c6eeb9
to
7032059
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
August 17, 2023 15:58
0487f17
to
9f33786
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
August 21, 2023 13:22
9f33786
to
8af248d
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
September 4, 2023 15:55
8af248d
to
8377456
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 10, 2023 15:41
8377456
to
700b4a2
Compare
renovate
bot
changed the title
chore(deps): update all (major)
fix(deps): update all (major)
Oct 10, 2023
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 14, 2023 19:28
700b4a2
to
b625469
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
February 7, 2024 06:20
346726e
to
5d8818c
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
February 26, 2024 21:10
e7d056b
to
c394534
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
March 26, 2024 16:29
c394534
to
01c3c4a
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
4 times, most recently
from
April 9, 2024 22:19
367faba
to
a0cb1cb
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
May 1, 2024 16:57
a0cb1cb
to
7661797
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
May 20, 2024 22:29
abd78f1
to
e8bb031
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
June 13, 2024 11:49
e8bb031
to
0112173
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
2 times, most recently
from
July 9, 2024 15:30
4c2737e
to
14c8153
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
September 19, 2024 15:38
14c8153
to
bf41624
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
October 1, 2024 15:10
bf41624
to
35f1ee5
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
3 times, most recently
from
October 29, 2024 16:34
78327b4
to
14a32da
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
8 times, most recently
from
November 21, 2024 02:35
2438990
to
3e7c53e
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
December 5, 2024 20:33
3e7c53e
to
36348e2
Compare
renovate
bot
force-pushed
the
renovate/major-all
branch
from
December 5, 2024 22:37
36348e2
to
9f19967
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:
^5.0.0
->^6.0.0
^16.11.12
->^22.0.0
v2
->v4
v2.4.1
->v4.1.0
v2.1.0
->v5.1.1
^8.3.0
->^9.0.0
^25.3.0
->^28.0.0
^7.0.4
->^9.0.0
^12.1.2
->^15.0.0
14
->22
^2.1.6
->^3.0.0
^2.5.1
->^3.0.0
^3.0.2
->^6.0.0
^4.5.3
->^5.0.0
Release Notes
actions/toolkit (@actions/github)
v6.0.0
v5.1.1
v5.1.0
v5.0.3
@actions/http-client
#1087v5.0.2
@actions/http-client
v5.0.1
actions/checkout (actions/checkout)
v4
Compare Source
v3
Compare Source
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.
codecov/codecov-action (codecov/codecov-action)
v5.1.1
Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.1.0..v5.1.1
v5.1.0
Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.0.7..v5.1.0
v5.0.7
Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.0.6..v5.0.7
v5.0.6
Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.0.5..v5.0.6
v5.0.5
Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.0.4..v5.0.5
v5.0.4
Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.0.3..v5.0.4
v5.0.3
Compare Source
What's Changed
inputs.disable_safe_directory
by @mkroening in https://github.com/codecov/codecov-action/pull/1666Full Changelog: https://github.com/codecov/codecov-action/compare/v5.0.2..v5.0.3
v5.0.2
Compare Source
What's Changed
Full Changelog: codecov/codecov-action@v5.0.1...v5.0.2
v5.0.1
Compare Source
What's Changed
Full Changelog: codecov/codecov-action@v5.0.0...v5.0.1
v5.0.0
Compare Source
v5 Release
v5
of the Codecov GitHub Action will use the Codecov Wrapper to encapsulate the CLI. This will help ensure that the Action gets updates quicker.Migration Guide
The
v5
release also coincides with the opt-out feature for tokens for public repositories. In theGlobal Upload Token
section of the settings page of an organization in codecov.io, you can set the ability for Codecov to receive a coverage reports from any source. This will allow contributors or other members of a repository to upload without needing access to the Codecov token. For more details see how to upload without a token.The following arguments have been added:
binary
gcov_args
gcov_executable
gcov_ignore
gcov_include
report_type
skip_validation
swift_project
You can see their usage in the
action.yml
file.What's Changed
Full Changelog: codecov/codecov-action@v4.6.0...v5.0.0
v4.6.0
Compare Source
What's Changed
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 becomes conflicted, 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.