Open
Conversation
e562176 to
d2264da
Compare
Author
|
47c739c to
4d84ffc
Compare
def8189 to
3b633e4
Compare
362a67c to
8e56f08
Compare
8e56f08 to
d79e640
Compare
d79e640 to
f786c7e
Compare
f786c7e to
5c106f0
Compare
30d29e5 to
dbba949
Compare
dbba949 to
6312c12
Compare
6312c12 to
0b4491b
Compare
0b4491b to
ae9d732
Compare
ae9d732 to
aec3f43
Compare
aec3f43 to
054bc71
Compare
054bc71 to
90c2eb2
Compare
90c2eb2 to
1b70a0b
Compare
1b70a0b to
433f67a
Compare
433f67a to
6799e0f
Compare
6799e0f to
1fec4b2
Compare
460345a to
016ea96
Compare
016ea96 to
26cd09a
Compare
26cd09a to
f8ec571
Compare
0bbddea to
d6ec68b
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
bb82bd7 to
7d81b64
Compare
7d81b64 to
c18acdc
Compare
f574e5d to
22520c2
Compare
22520c2 to
40d14cd
Compare
a90caed to
e512d79
Compare
9ec86f7 to
68a4ed2
Compare
68a4ed2 to
02b41c9
Compare
4588c84 to
4b3024e
Compare
24ec0ae to
9258c52
Compare
9258c52 to
edc5d7f
Compare
edc5d7f to
aa2467b
Compare
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
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.7→v5.0.3v3→v6v2→v6v2→v6v1.9.0→v5.0.0v0.0.5→v1.1.3v1.22.5→v3.6.2v3→v920.04→24.04Release Notes
actions/cache (actions/cache)
v5.0.3Compare Source
What's Changed
@actions/cacheto v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)@actions/coreto v2.0.3Full Changelog: actions/cache@v5...v5.0.3
v5.0.2Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
v4.3.0Compare Source
What's Changed
v4.3.0release by @Link- in #1655New Contributors
Full Changelog: actions/cache@v4...v4.3.0
v4.2.4Compare Source
What's Changed
@actions/cacheto4.0.5and move@protobuf-ts/pluginto dev depdencies by @Link- in #16344.2.4by @Link- in #1636New Contributors
Full Changelog: actions/cache@v4...v4.2.4
v4.2.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4.2.2...v4.2.3
v4.2.2Compare Source
What's Changed
Full Changelog: actions/cache@v4.2.1...v4.2.2
v4.2.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4.2.0...v4.2.1
v4.2.0Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4orv3as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0orv3.4.0If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.11.1.30.38.3Full Changelog: actions/cache@v4.1.2...v4.2.0
v4.1.2Compare Source
What's Changed
isGheslogic by @jww3 in #14744.1.2release by @Link- in #1477New Contributors
Full Changelog: actions/cache@v4.1.1...v4.1.2
v4.1.1Compare Source
What's Changed
cache-hitoutput by @joshmgross in #1467Full Changelog: actions/cache@v4.1.0...v4.1.1
v4.1.0Compare Source
What's Changed
save-alwaysinput by @joshmgross in #1452New Contributors
Full Changelog: actions/cache@v4.0.2...v4.1.0
v4.0.2Compare Source
What's Changed
fail-on-cache-missnot working by @cdce8p in #1327Full Changelog: actions/cache@v4.0.1...v4.0.2
v4.0.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4...v4.0.1
v4.0.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v4.0.0
v3.5.0Compare Source
actions/cacheto v4.1.0Full Changelog: actions/cache@v3...v3.5.0
v3.4.3Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.2...v3.4.3
v3.4.2Compare Source
What's Changed
Full Changelog: actions/cache@v3.4.0...v3.4.2
v3.4.1Compare Source
v3.4.0Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4orv3as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0orv3.4.0If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.11.1.30.38.3Full Changelog: actions/cache@v3.3.3...v3.4.0
v3.3.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.3
v3.3.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.3.2
v3.3.1Compare Source
What's Changed
Full Changelog: actions/cache@v3...v3.3.1
v3.3.0Compare Source
What's Changed
lookup-onlyoption by @cdce8p in #1041New Contributors
Full Changelog: actions/cache@v3...v3.3.0
v3.2.6Compare Source
What's Changed
Full Changelog: actions/cache@v3...v3.2.6
v3.2.5Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.5
v3.2.4Compare Source
What's Changed
set-outputcommand is deprecated by @siguikesse in #1046fail-on-cache-missoption by @cdce8p in #1036New Contributors
Full Changelog: actions/cache@v3...v3.2.4
v3.2.3Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.3
v3.2.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3.2.1...v3.2.2
v3.2.1Compare Source
What's Changed
Full Changelog: actions/cache@v3.2.0...v3.2.1
v3.2.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.2.0
v3.0.11Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.0.11
v3.0.10Compare Source
restore-keysin README.mdv3.0.9Compare Source
v3.0.8Compare Source
What's Changed
zstdnot working for windows on gnu tar in issues.SEGMENT_DOWNLOAD_TIMEOUT_MIN. Default is 60 minutes.v3.0.7Compare Source
What's Changed
v3.0.6Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v3...v3.0.6
v3.0.5Compare Source
Removed error handling by consuming actions/cache 3.0 toolkit, Now cache server error handling will be done by toolkit.
v3.0.4Compare Source
In this release, we have fixed the tar creation error while trying to create it with path as
~/home folder onubuntu-latest.v3.0.3Compare Source
Fixed avoiding empty cache save when no files are available for caching. (#624)
v3.0.2Compare Source
This release adds the support for dynamic cache size cap on GHES.
v3.0.1Compare Source
v3.0.0Compare Source
This change adds a minimum runner version(node12 -> node16), which can break users using an out-of-date/fork of the runner. This would be most commonly affecting users on GHES 3.3 or before, as those runners do not support node16 actions and they can use actions from github.com via github connect or manually copying the repo to their GHES instance.
Few dependencies and cache action usage examples have also been updated.
v2.1.8: Updating actions/core to version 1.10.0Compare Source
The ::save-state and ::set-output are deprecated. The newer version of actions/core >1.10.0 uses the new syntax for save and set output. After this change, customers using actions/cache@v2 won't see deprecation warning message.
actions/checkout (actions/checkout)
v6Compare Source
v5Compare Source
v4Compare Source
url-helper.tsnow leverages well-known environment variables by @jww3 in #1941isGhesby @jww3 in #1946actions/setup-go (actions/setup-go)
v6Compare Source
v5Compare Source
v4Compare Source
v3Compare Source
codfish/semantic-release-action (codfish/semantic-release-action)
v5.0.0Compare Source
Features
BREAKING CHANGES
Upgraded to semantic-release v25 with breaking changes in the GitHub plugin.
Any breaking changes from v25 apply to this github action version except for
Node version requirements. Because this is a docker-based github action, the
version of node in use is defined inside of the docker image, not by the
consuming runner or your code.
@semantic-release/github v12: The GitHub plugin no longer uses the GitHub
Search API (
/search/issuesendpoint). It now uses GraphQL queries exclusivelyfor issue retrieval. This architectural change may affect issue management in
edge cases. See github plugin v12 release notes.
semantic-release v25: Upgraded from v24.2.7 to v25.0.3
npm OIDC Trusted Publishing Support: The upgrade to @semantic-release/npm v13 enables
support for npm's new OIDC-based trusted publishing. This allows publishing to npm without
long-lived access tokens by using GitHub's OIDC token provider. This is more secure and
eliminates the need to store
NPM_TOKENas a repository secret when publishing from GitHubActions. See npm documentation
for configuration details.
Node.js: Upgraded to v24.13.0 (bundled in Docker, not a breaking change for users)
@actions/core: Upgraded to v3.0.0 (internal implementation only)
could affect issue management behavior
@v5id-token: writepermission to your workflow jobNPM_TOKENsecret (you won't need it anymore!)v5uses semantic-release v25 & node v24.13.0v4uses semantic-release v24 & node v22.18.0v3uses semantic-release v22 & node v20.9v2uses semantic-release v20 & node v18.7Compare: codfish/semantic-release-action@v4.0.1...v5.0.0
v4.0.1Compare Source
Bug Fixes
v4.0.0Compare Source
Features
BREAKING CHANGES
v3.5.0Compare Source
Features
v3.4.1Compare Source
Bug Fixes
v3.4.0Compare Source
Features
v3.3.0Compare Source
Features
v3.2.0Compare Source
Features
v3.1.1Compare Source
Bug Fixes
v3.1.0Compare Source
Bug Fixes
Features
v3.0.0Compare Source
Bug Fixes
Configuration
📅 Schedule: 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.
👻 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.