:arrow_up: Updates actions/cache action to v5 by renovate[bot] · Pull Request #674 · AlexRogalskiy/github-action-charts

Update README.md by @nebuk89 in #1620
Upgrade @actions/cache to 4.0.5 and move @protobuf-ts/plugin to dev depdencies by @Link- in #1634
Prepare release 4.2.4 by @Link- in #1636

New Contributors

@nebuk89 made their first contribution in #1620

Full Changelog: actions/cache@v4...v4.2.4

`v4.2.3`

Compare Source

What's Changed

Update to use @actions/cache 4.0.3 package & prepare for new release by @salmanmkc in #1577 (SAS tokens for cache entries are now masked in debug logs)

New Contributors

@salmanmkc made their first contribution in #1577

Full Changelog: actions/cache@v4.2.2...v4.2.3

`v4.2.2`

Compare Source

What's Changed

[!IMPORTANT]
As a reminder, there were important backend changes to release v4.2.0, see those release notes and the announcement for more details.

Bump @actions/cache to v4.0.2 by @robherley in #1560

Full Changelog: actions/cache@v4.2.1...v4.2.2

`v4.2.1`

Compare Source

What's Changed

[!IMPORTANT]
As a reminder, there were important backend changes to release v4.2.0, see those release notes and the announcement for more details.

docs: GitHub is spelled incorrectly in caching-strategies.md by @janco-absa in #1526
docs: Make the "always save prime numbers" example more clear by @Tobbe in #1525
Update force deletion docs due a recent deprecation by @sebbalex in #1500
Bump @actions/cache to v4.0.1 by @robherley in #1554

New Contributors

@janco-absa made their first contribution in #1526
@Tobbe made their first contribution in #1525
@sebbalex made their first contribution in #1500

Full Changelog: actions/cache@v4.2.0...v4.2.1

`v4.2.0`

Compare Source

⚠️ Important Changes

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 v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).

If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0

If 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:

@actions/core: 1.11.1
@actions/io: 1.1.3
@vercel/ncc: 0.38.3

Full Changelog: actions/cache@v4.1.2...v4.2.0

`v4.1.2`

Compare Source

What's Changed

Add Bun example by @idleberg in #1456
Revise isGhes logic by @jww3 in #1474
Bump braces from 3.0.2 to 3.0.3 by @dependabot in #1475
Add dependabot.yml to enable automatic dependency upgrades by @Link- in #1476
Bump actions/checkout from 3 to 4 by @dependabot in #1478
Bump actions/stale from 3 to 9 by @dependabot in #1479
Bump github/codeql-action from 2 to 3 by @dependabot in #1483
Bump actions/setup-node from 3 to 4 by @dependabot in #1481
Prepare 4.1.2 release by @Link- in #1477

New Contributors

@idleberg made their first contribution in #1456
@jww3 made their first contribution in #1474
@Link- made their first contribution in #1476

Full Changelog: actions/cache@v4.1.1...v4.1.2

`v4.1.1`

Compare Source

What's Changed

Restore original behavior of cache-hit output by @joshmgross in #1467

Full Changelog: actions/cache@v4.1.0...v4.1.1

`v4.1.0`

Compare Source

What's Changed

Fix cache-hit output when cache missed by @fchimpan in #1404
Deprecate save-always input by @joshmgross in #1452

New Contributors

@ottlinger made their first contribution in #1437
@Olegt0rr made their first contribution in #1377
@fchimpan made their first contribution in #1404
@x612skm made their first contribution in #1434
@todgru made their first contribution in #1311
@Jcambass made their first contribution in #1463
@mackey0225 made their first contribution in #1462
@quatquatt made their first contribution in #1445

Full Changelog: actions/cache@v4.0.2...v4.1.0

`v4.0.2`

Compare Source

What's Changed

Fix fail-on-cache-miss not working by @cdce8p in #1327

Full Changelog: actions/cache@v4.0.1...v4.0.2

`v4.0.1`

Compare Source

What's Changed

Update README.md by @yacaovsnc in #1304
Update examples by @yacaovsnc in #1305
Update actions/cache publish flow by @bethanyj28 in #1340
Update @actions/cache by @bethanyj28 in #1341

New Contributors

@yacaovsnc made their first contribution in #1304

Full Changelog: actions/cache@v4...v4.0.1

`v4.0.0`

Compare Source

What's Changed

Update action to node20 by @takost in #1284
feat: save-always flag by @to-s in #1242

New Contributors

@takost made their first contribution in #1284
@to-s made their first contribution in #1242

Full Changelog: actions/cache@v3...v4.0.0

`v4`

Compare Source

`v3.5.0`

Compare Source

Bump actions/cache to v4.1.0

Full Changelog: actions/cache@v3...v3.5.0

`v3.4.3`

Compare Source

What's Changed

Bump @actions/cache to v4.0.2 by @robherley

Full Changelog: actions/cache@v3.4.2...v3.4.3

`v3.4.2`

Compare Source

What's Changed

[!IMPORTANT]
As a reminder, there were important backend changes to release v3.4.0, see those release notes and the announcement for more details.

Bump @actions/cache to v4.0.1 by @robherley in #1554

Full Changelog: actions/cache@v3.4.0...v3.4.2

`v3.4.1`

Compare Source

[!WARNING]
This version was incorrectly released using a SHA pointing to a newer version for immutable actions only. Please use v3.4.2 (or v3) instead.

`v3.4.0`

Compare Source

⚠️ Important Changes

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 v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).

If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0

If 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:

@actions/core: 1.11.1
@actions/io: 1.1.3
@vercel/ncc: 0.38.3

Full Changelog: actions/cache@v3.3.3...v3.4.0

`v3.3.3`

Compare Source

What's Changed

Cache v3.3.3 by @robherley in #1302

New Contributors

@robherley made their first contribution in #1302

Full Changelog: actions/cache@v3...v3.3.3

`v3.3.2`

Compare Source

What's Changed

Fixed readme with new segment timeout values by @kotewar in #1133
Readme fixes by @kotewar in #1134
Updated description of the lookup-only input for main action by @kotewar in #1130
Change two new actions mention as quoted text by @bishal-pdMSFT in #1131
Update Cross-OS Caching tips by @pdotl in #1122
Bazel example (Take #2️⃣) by @vorburger in #1132
Remove actions to add new PRs and issues to a project board by @jorendorff in #1187
Consume latest toolkit and fix dangling promise bug by @chkimes in #1217
Bump action version to 3.3.2 by @bethanyj28 in #1236

New Contributors

@vorburger made their first contribution in #1132
@jorendorff made their first contribution in #1187
@chkimes made their first contribution in #1217
@bethanyj28 made their first contribution in #1236

Full Changelog: actions/cache@v3...v3.3.2

`v3.3.1`

Compare Source

What's Changed

Reduced download segment size to 128 MB and timeout to 10 minutes by @kotewar in #1129

Full Changelog: actions/cache@v3...v3.3.1

`v3.3.0`

Compare Source

What's Changed

Bug: Permission is missing in cache delete example by @kotokaze in #1123
Add lookup-only option by @cdce8p in #1041

New Contributors

@kotokaze made their first contribution in #1123

Full Changelog: actions/cache@v3...v3.3.0

`v3.2.6`

Compare Source

What's Changed

Updated branch in Force deletion of caches by @t-dedah in #1108
Fix zstd not being used after zstd version upgrade to 1.5.4 on hosted runners by @pdotl in #1118

Full Changelog: actions/cache@v3...v3.2.6

`v3.2.5`

Compare Source

What's Changed

Rewrite readmes by @jsoref in #1085
Fixed typos and formatting in docs by @kotewar in #1076
Fixing paths for OSes by @kotewar in #1101
Release patch version update by @Phantsure in #1105

New Contributors

@jsoref made their first contribution in #1085

Full Changelog: actions/cache@v3...v3.2.5

`v3.2.4`

Compare Source

What's Changed

Update json5 package version by @vsvipul in #1065
Cache recipes for cache, restore and save actions by @kotewar in #1055
Add gnu tar and zstd as pre-requisites for windows self-hosted runners by @pdotl in #1068
Fix a whitespace typo by @kurtmckee in #1074
📝 #1045 update using the set-output command is deprecated by @siguikesse in #1046
Fix referenced output key in save action readme by @ruudk in #1061
Update workflows to use reusable-workflows by @jongwooo in #1066
Introduce add-to-project step & rename workflow files by @pallavx in #1077
chore: Fix syntax error typo by @vHeemstra in #1081
Update caching-strategies.md by @kpfleming in #1084
Added another usage hint to foresee #1072 by @maybeec in #1089
Add fail-on-cache-miss option by @cdce8p in #1036

New Contributors

@kurtmckee made their first contribution in #1074
@siguikesse made their first contribution in #1046
@ruudk made their first contribution in #1061
@pallavx made their first contribution in #1077
@vHeemstra made their first contribution in #1081
@kpfleming made their first contribution in #1084
@maybeec made their first contribution in #1089
@cdce8p made their first contribution in #1036

Full Changelog: actions/cache@v3...v3.2.4

`v3.2.3`

Compare Source

What's Changed

Add Mint example by @uhooi in #1051
Fixed broken link by @kotewar in #1057
Add support to opt-in enable cross-os caching on windows by @Phantsure in #1056
Release support for cross-os caching as opt-in feature by @Phantsure in #1060

New Contributors

@uhooi made their first contribution in #1051

Full Changelog: actions/cache@v3...v3.2.3

`v3.2.2`

Compare Source

What's Changed

Fix formatting error in restore/README.md by @me-and in #1044
save/README.md: Fix typo in example by @mmuetzel in #1040
README.md: remove outdated Windows cache tip link by @me-and in #1042
Revert compression changes related to windows but keep version logging by @Phantsure in #1049

New Contributors

@me-and made their first contribution in #1044
@mmuetzel made their first contribution in #1040

Full Changelog: actions/cache@v3.2.1...v3.2.2

`v3.2.1`

Compare Source

What's Changed

Release compression related changes for windows by @Phantsure in #1039
Upgrade codeql to v2 by @Phantsure in #1023

Full Changelog: actions/cache@v3.2.0...v3.2.1

`v3.2.0`

Compare Source

What's Changed

fix wrong timeout env var key in README.md by @walterddr in #959
Updated release doc with correct env variable by @kotewar in #960
Create pull_request_template.md by @pdotl in #963
Update README with clearer info about cache-hit and its value by @kotewar in #961
Change datadog/squid to Ubuntu/squid in CI check by @bishal-pdMSFT in #976
Add more details to version section in readme by @bishal-pdMSFT in #971
Update hashFiles documentation reference by @asaf400 in #979
Updated link for cache segment download info by @kotewar in #986
Readme update for deleting caches by @t-dedah in #981
Add oncall logic to assign issues and PRs by @vsvipul in #997
Bump minimatch from 3.0.4 to 3.1.2 by @dependabot in #998
Revert "Bump minimatch from 3.0.4 to 3.1.2" by @vsvipul in #1005
Fix npm vulnerability by @Phantsure in #1007
refactor: Use early return pattern to avoid nested conditions by @jongwooo in #1013
Use cache in check-dist.yml by @jongwooo in #1004
chore: Use built-in cache action to cache dependencies by @jongwooo in #1014
Updated node example by @t-dedah in #1008
Fix: Node npm doc example by @apascualm in #1026
docs: fix an invalid link in workarounds.md by @teatimeguest in #929
General Availability release for granular cache by @kotewar in #1035 More details here on beta release.

New Contributors

@walterddr made their first contribution in #959
@asaf400 made their first contribution in #979
@jongwooo made their first contribution in #1013
@apascualm made their first contribution in #1026
@teatimeguest made their first contribution in #929

Full Changelog: actions/cache@v3...v3.2.0

`v3.0.11`

Compare Source

What's Changed

Call out cache not saved on hit by @Phantsure in #946
Update @actions/core to 1.10.0 by @rentziass in #950
Update cache to use @actions/core@^1.10.0 by @pdotl in #956

New Contributors

@rentziass made their first contribution in #950

Full Changelog: actions/cache@v3...v3.0.11

`v3.0.10`

Compare Source

Fix a bug with sorting inputs.
Update definition for restore-keys in README.md

`v3.0.9`

Compare Source

Enhanced the warning message for cache unavailability in case of GHES.

`v3.0.8`

Compare Source

What's Changed

Fix zstd not working for windows on gnu tar in issues.
Allow users to provide a custom timeout as input for aborting cache segment download using the environment variable SEGMENT_DOWNLOAD_TIMEOUT_MIN. Default is 60 minutes.

`v3.0.7`

Compare Source

What's Changed

Fix for the download stuck problem has been added in actions/cache for users who were intermittently facing the issue. As part of this fix, new timeout has been introduced in the download step to stop the download if it doesn't complete within an hour and run the rest of the workflow without erroring out.

`v3.0.6`

Compare Source

What's Changed

Add example for clojure lein project dependencies by @shivamarora1 in PR #835
Update toolkit's cache npm module to latest. Bump cache version to v3.0.6 by @pdotl in PR #887
Fix issue #809 where cache save/restore was failing for Amazon Linux 2 runners due to older tar version
Fix issue #833 where cache save was not working for caching github workspace directory

New Contributors

@shivamarora1 made their first contribution in #835
@pdotl made their first contribution in #887

Full Changelog: actions/cache@v3...v3.0.6

`v3.0.5`

Compare Source

Removed error handling by consuming actions/cache 3.0 toolkit, Now cache server error handling will be done by toolkit.

`v3.0.4`

Compare Source

In this release, we have fixed the tar creation error while trying to create it with path as ~/ home folder on ubuntu-latest.

`v3.0.3`

Compare Source

Fixed avoiding empty cache save when no files are available for caching. (#624)

`v3.0.2`

Compare Source

This release adds the support for dynamic cache size cap on GHES.

`v3.0.1`

Compare Source

Added support for caching from GHES 3.5.
Fixed download issue for files > 2GB during restore.

`v3.0.0`

Compare 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.

`v3`

Compare Source

`v2.1.8`: Updating actions/core to version 1.10.0

Compare 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.

`v2.1.7`

Compare Source

Support 10GB cache upload using the latest version 1.0.8 of @actions/cache

`v2.1.6`

Compare Source

Catch unhandled "bad file descriptor" errors that sometimes occurs when the cache server returns non-successful response (#596)

`v2.1.5`

Compare Source

Fix permissions error seen when extracting caches with GNU tar that were previously created using BSD tar (#527)

`v2.1.4`

Compare Source

Make caching more verbose #650
Use GNU tar on macOS if available #701

`v2.1.3`

Compare Source

Upgrades @actions/core to v1.2.6 for CVE-2020-15228. This action was not using the affected methods.
Fix error handling in uploadChunk where 400-level errors were not being detected and handled correctly

`v2.1.2`

Compare Source

Adds input to limit the chunk upload size, useful for self-hosted runners with slower upload speeds
No-op when executing on GHES

`v2.1.1`

Compare Source

Update @actions/cache package to v1.0.2 which allows cache action to use posix format when taring files.

`v2.1.0`

Compare Source

Replaces the http-client with the Azure Storage SDK for NodeJS when downloading cache content from Azure. This should help improve download performance and reliability as the SDK downloads files in 4 MB chunks, which can be parallelized and retried independently
Display download progress and speed

`v2.0.0`

Compare Source

Initial v2 release

What's new in v2

Added support for multiple paths (#16), glob patterns, and single file caches (#33)
Increased performance and improved cache sizes using zstd for compression for Linux and macOS runners (#184)
Allowed caching for all events with a ref (#63)
Created the @actions/cache npm package to allow other actions to utilize caching (#55)
Added a best-effort step to delete the archive after extraction to reduces storage space (#209)

`v2`

Compare Source

`v1.2.1`: Updating actions/core to version 1.10.0

Compare 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@v1 won't see deprecation warning message.

`v1.2.0`

Compare Source

Bug Fixes

Fall back to GNU tar on older versions of Windows that do not have BSD tar installed (#252)
Fixed chunk upload retry logic (#305)

Improvements

Improved reliability of the download cache APIs (#269)
Added retries to API calls that failed due to retryable errors (#306)
Improved error handling during both cache upload (#300) and download (#284)

`v1.1.2`

Compare Source

Other

Updating action name back to "Cache" to fix the marketplace links (https://github.com/marketplace/actions/cache)

`v1.1.1`

Compare Source

Improvements

Increase cache size limit to 5 GB (#168)
Add proxy support (#166)

`v1.1.0`

Compare Source

Bug Fixes

Use BSD tar on windows (#126) to support self-hosted runners (#91)

Improvements

Improved reliability and speed of cache upload via chunked APIs (#128)
Increased per-cache size limit to 2 GB to match the per-repo limit (#6)

`v1.0.3`

Compare Source

Improvements

Remove validation failures and warning annotations (#108)
Mask download URL in logs (#110)

`v1.0.2`

Compare Source

Bug Fixes

Fixed race condition when restoring a cache (#100)

Improvements

Provide better errors for unsupported event types (#68)
Format cache size and display on info (#85)

`v1.0.1`

Compare Source

Improvements

Bump cache limit to 400MB (#61)
Tweak 'Cache not found' message (#54)

Configuration

📅 Schedule: (in timezone Europe/Moscow)

Branch creation
- "after 10pm every weekday,before 5am every weekday,every weekend"
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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

github-actions · 2025-12-12T22:51:57Z

🏷️ [bumpr]
Next version:v1.14.1
Changes:v1.14.0...AlexRogalskiy:renovate/actions-cache-5.x

github-actions · 2025-12-12T22:51:58Z

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Secrets Audit	0	426	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

socket-security · 2026-04-19T10:07:24Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint@7.19.0
	jest@27.0.0-next.2
	expect@26.6.2
	cz-conventional-changelog@3.3.0
	git-cz@4.7.6
	husky@4.3.8
	eslint-plugin-github@4.1.1
	eslint-plugin-import@2.22.1
	editorconfig-checker@3.3.0
	eslint-config-prettier@6.15.0
	jest-circus@26.6.3
	eslint-plugin-prettier@3.3.1
	lint-staged@10.5.4
	eslint-plugin-jest@23.20.0

View full report

socket-security · 2026-04-19T10:07:25Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Critical CVE: npm `form-data` uses unsafe random function in form-data for choosing boundary CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 2.5.4 From: package-lock.json → `npm/form-data@2.3.3` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/form-data@2.3.3`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: Handlebars.js has JavaScript Injection via AST Type Confusion CVE: GHSA-2w6w-674q-4c4q Handlebars.js has JavaScript Injection via AST Type Confusion (CRITICAL) Affected versions: >= 4.0.0 < 4.7.9 Patched version: 4.7.9 From: package-lock.json → `npm/@semantic-release/release-notes-generator@7.3.5` → `npm/handlebars@4.7.7` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/handlebars@4.7.7`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: npm `json-schema` is vulnerable to Prototype Pollution CVE: GHSA-896r-f27r-55mw json-schema is vulnerable to Prototype Pollution (CRITICAL) Affected versions: < 0.4.0 Patched version: 0.4.0 From: package-lock.json → `npm/json-schema@0.2.3` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/json-schema@0.2.3`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: Prototype Pollution in npm `minimist` CVE: GHSA-xvch-5gv4-984h Prototype Pollution in minimist (CRITICAL) Affected versions: >= 1.0.0 < 1.2.6; < 0.2.4 Patched version: 1.2.6 From: package-lock.json → `npm/cz-conventional-changelog@3.3.0` → `npm/jest@27.0.0-next.2` → `npm/jest-circus@26.6.3` → `npm/@semantic-release/release-notes-generator@7.3.5` → `npm/minimist@1.2.5` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/minimist@1.2.5`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `npm` is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: package-lock.json → `npm/@semantic-release/npm@5.3.5` → `npm/npm@6.14.11` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/npm@6.14.11`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

github-actions

Scan Summary

Tool	Critical	High	Medium	Low	Status
Secrets Audit	0	427	0	0	❌

Recommendation

Please review the findings from Code scanning alerts before approving this pull request. You can also configure the build rules or add suppressions to customize this bot 👍

renovate Bot added bump:patch labels Dec 12, 2025

auto-assign Bot requested a review from AlexRogalskiy December 12, 2025 22:51

github-actions Bot reviewed Dec 12, 2025

View reviewed changes

github-actions Bot added the security findings label Dec 12, 2025

github-actions Bot removed bump:patch labels Apr 18, 2026

⬆️ Updates actions/cache action to v5

a02c0a6

renovate Bot force-pushed the renovate/actions-cache-5.x branch from 737f878 to a02c0a6 Compare April 19, 2026 10:06

github-actions Bot reviewed Apr 19, 2026

View reviewed changes

github-actions Bot added the security findings label Apr 19, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

⬆️ Updates actions/cache action to v5#674

⬆️ Updates actions/cache action to v5#674
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/actions-cache-5.x

renovate Bot commented Dec 12, 2025 •

edited

Loading

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

github-actions Bot left a comment

Uh oh!

socket-security Bot commented Apr 19, 2026

Uh oh!

socket-security Bot commented Apr 19, 2026

Uh oh!

github-actions Bot left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate Bot commented Dec 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

What's Changed

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

⚠️ Important Changes

Minor changes

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

What's Changed

⚠️ Important Changes

Minor changes

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

What's Changed

What's Changed

New Contributors

v2.1.8: Updating actions/core to version 1.10.0

What's new in v2

v1.2.1: Updating actions/core to version 1.10.0

Bug Fixes

Improvements

Other

Improvements

Bug Fixes

Improvements

Improvements

Bug Fixes

Improvements

Improvements

Configuration

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

github-actions Bot left a comment

renovate Bot commented Dec 12, 2025 •

edited

Loading

`v2.1.8`: Updating actions/core to version 1.10.0

`v1.2.1`: Updating actions/core to version 1.10.0