Update @actions/core 2.0.2 → 3.0.0 (major)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​actions/core (2.0.2 → 3.0.0) · Repo · Changelog

Release Notes

3.0.0 (from changelog)

• Breaking change: Package is now ESM-only
  • CommonJS consumers must use dynamic import() instead of require()

2.0.3 (from changelog)

• Bump @actions/http-client to 3.0.2

Does any of this look wrong? Please let us know.

🆕 @​actions/http-client (added, 4.0.0)

🆕 @​actions/http-client (added, 3.0.2)

🆕 @​actions/core (added, 2.0.3)

🆕 @​actions/core (added, 3.0.0)

🆕 @​actions/exec (added, 3.0.0)

🆕 @​actions/io (added, 3.0.2)

🆕 undici (added, 6.23.0)

🗑️ @​actions/http-client (removed)

🗑️ @​actions/core (removed)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[guibranco]

Automatically approved by gstraccini[bot]

[deepsource-io]

Here's the code health analysis summary for commits 7b7bcb5..e50fc15. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Test coverage	⚠️ Artifact not reported	Timed out: Artifact was never reported	View Check ↗
JavaScript	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​actions/​core@​2.0.2 ⏵ 3.0.0				+3

View full report

[guibranco]

@depfu merge

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Embedded URLs or IPs: npm undici URLs: https://github.com/nodejs/undici/issues/2630, https://github.com/node-fetch/fetch-blob/blob/8ab587d34080de94140b54f07168451e7d0b655e/index.js#L229-L241, https://developer.mozilla.org/en-US/docs/Web/API/URL/URL:, https://github.com/nodejs/node/pull/38505/files, https://github.com/nodejs/node/pull/46528, https://github.com/nodejs/undici/pull/319, https://tools.ietf.org/html/rfc7230#section-3.2.6, https://github.com/nodejs/node/blob/main/lib/_http_common.js, https://www.rfc-editor.org/rfc/rfc9110#field.content-range, https://fetch.spec.whatwg.org/#concept-main-fetch, https://fetch.spec.whatwg.org/#concept-scheme-fetch, https://github.com/nodejs/undici/issues/1776, https://github.com/web-platform-tests/wpt/blob/7b0ebaccc62b566a1965396e5be7bb2bc06f841f/FileAPI/url/resources/fetch-tests.js#L52-L56, https://github.com/nodejs/undici/issues/1193., https://fetch.spec.whatwg.org/#http-redirect-fetch, https://fetch.spec.whatwg.org/#cors-non-wildcard-request-header-name, https://fetch.spec.whatwg.org/#authentication-entries, https://github.com/whatwg/fetch/issues/1293, https://fetch.spec.whatwg.org/#http-network-fetch, https://tools.ietf.org/html/rfc7540#section-8.3, https://tools.ietf.org/html/rfc7231#section-4.3.1, https://tools.ietf.org/html/rfc7231#section-4.3.2, https://tools.ietf.org/html/rfc7231#section-4.3.5, https://tools.ietf.org/html/rfc7230#section-3.3.2, https://github.com/nodejs/undici/issues/2046, https://websockets.spec.whatwg.org/#feedback-from-the-protocol, https://datatracker.ietf.org/doc/html/rfc6455#section-7.1.4, https://tools.ietf.org/html/rfc7230#section-6.3.2, https://mimesniff.spec.whatwg.org/#parse-a-mime-type, https://fetch.spec.whatwg.org/#body-mixin, https://developer.mozilla.org/en-US/docs/Web/API/Blob, https://developer.mozilla.org/en-US/docs/Web/API/File, https://github.com/curl/curl/blob/3434c6b46e682452973972e8313613dfa58cd690/lib/mime.c#L1029-L1030, https://github.com/form-data/form-data/issues/63, https://fetch.spec.whatwg.org/#bodyinit-safely-extract, https://fetch.spec.whatwg.org/#concept-body-clone, https://fetch.spec.whatwg.org/#concept-body-consume-body, https://fetch.spec.whatwg.org/#body-unusable, https://infra.spec.whatwg.org/#parse-json-bytes-to-a-javascript-value, https://fetch.spec.whatwg.org/#concept-body-mime-type, CacheStorage.open, https://tools.ietf.org/html/rfc2616, https://tools.ietf.org/html/rfc7230, https://github.com/chromium/chromium/blob/94.0.4604.1/third_party/blink/renderer/core/fetch/response.cc#L116, https://fetch.spec.whatwg.org/#header-name, https://fetch.spec.whatwg.org/#header-value, https://w3c.github.io/webappsec-referrer-policy/#set-requests-referrer-policy-on-redirect, https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy#specify_a_fallback_policy, https://fetch.spec.whatwg.org/#cross-origin-resource-policy-check, https://fetch.spec.whatwg.org/#concept-cors-check, https://fetch.spec.whatwg.org/#concept-tao-check, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-dest-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-mode-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-site-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-user-header, https://fetch.spec.whatwg.org/#append-a-request-origin-header, https://html.spec.whatwg.org/multipage/origin.html#clone-a-policy-container, https://w3c.github.io/webappsec-referrer-policy/#determine-requests-referrer, https://github.com/web-platform-tests/wpt/commit/e4c5cc7a5e48093220528dfdd1c4012dc3837a0e, https://webidl.spec.whatwg.org/#iterator-result, https://webidl.spec.whatwg.org/#dfn-iterator-prototype-object, https://fetch.spec.whatwg.org/#body-fully-read, https://infra.spec.whatwg.org/#isomorphic-encode, https://streams.spec.whatwg.org/#readablestreamdefaultreader-read-all-bytes, https://streams.spec.whatwg.org/#read-loop, https://fetch.spec.whatwg.org/#is-local, https://fetch.spec.whatwg.org/#simple-range-header-value, https://fetch.spec.whatwg.org/#build-a-content-range, https://fetch.spec.whatwg.org/#concept-header-list-get-decode-split, https://encoding.spec.whatwg.org/#utf-8-decode, https://fetch.spec.whatwg.org/#response-create, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry, https://fetch.spec.whatwg.org/#typedefdef-xmlhttprequestbodyinit, https://fetch.spec.whatwg.org/#bodyinit Location: Package overview From: package-lock.json → npm/@actions/core@3.0.0 → npm/undici@6.23.0 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@6.23.0. 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.
Block		Potential code anomaly (AI signal): npm undici is 100.0% likely to have a medium risk anomaly Notes: The analyzed code appears to implement a standard in-memory cache batch operation flow (put/delete) with careful handling of response bodies by buffering and storing bytes for caching. No signs of malware, data exfiltration, backdoors, or obfuscated behavior were found. The primary security considerations relate to memory usage from buffering potentially large response bodies and ensuring robust validation within batch operations to prevent cache state corruption. Overall risk is moderate, driven by in-memory data handling rather than external communication. Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/@actions/core@3.0.0 → npm/undici@6.23.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@6.23.0. 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.
Block		Potential code anomaly (AI signal): npm undici is 100.0% likely to have a medium risk anomaly Notes: The script performs an in-place, lossy re-encoding of a local file from UTF-8 to Latin-1 and rewrites it without backups or validation. This is unsafe due to potential data loss and code corruption, and could be exploited to tamper with source files in a supply chain. It does not exhibit active malware behavior, but its destructive nature warrants removal or strict safeguards (backups, explicit intent, error handling). Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/@actions/core@3.0.0 → npm/undici@6.23.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@6.23.0. 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