chore(npm): bump @actions/core from 1.11.1 to 3.0.0 in the actions-toolkit group

[dependabot]

Bumps the actions-toolkit group with 1 update: @actions/core.

Updates @actions/core from 1.11.1 to 3.0.0

Changelog

Sourced from @​actions/core's changelog.

3.0.0

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

2.0.3

• Bump @actions/http-client to 3.0.2

2.0.1

• Bump @​actions/exec from 1.1.1 to 2.0.0 #2199

2.0.0

• Add support for Node 24 #2110
• Bump @​actions/http-client from 2.0.1 to 3.0.0

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​actions/core since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Labels

The following labels could not be found: dependencies, npm. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[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@​1.11.1 ⏵ 3.0.0

View full report

[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		Potential code anomaly (AI signal): npm undici is 100.0% likely to have a medium risk anomaly Notes: The code is a focused error-handling helper for HTTP responses that safely parses small payloads to include in an error object. It includes protective measures (chunk limits, controlled parsing, microtask-based callbacks) but uses unusual, brittle content-type checks and suppresses stack traces for debugging concealment. There is no evidence of malicious activity, data exfiltration, or backdoors within this fragment. The main risk is potential silent data loss if payloads exceed the chunk limit or mismatched content-type handling leads to missing payloads, but this is a functional trade-off rather than malicious. Suggested improvements include robust content-type parsing, clearer error signaling when payload is truncated, and optional logging to aid debugging without exposing stack traces in production. Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/@actions/core@3.0.0 → npm/undici@6.24.1 ℹ 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.24.1. 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.24.1 ℹ 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.24.1. 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.24.1 ℹ 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.24.1. 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 implements a conventional HTTP/WebSocket-like upgrade handler with proper input validation, abort signal integration, and asynchronous callback management. It does not exhibit malicious activity such as data exfiltration or backdoors. The deliberate onHeaders error path is consistent with protocol expectations to reject non-upgrade responses. Overall security risk remains low to moderate, contingent on integration context, but no indicators of malware or obfuscation are detected in this fragment. Confidence: 1.00 Severity: 0.60 From: package-lock.json → npm/@actions/core@3.0.0 → npm/undici@6.24.1 ℹ 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.24.1. 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		Embedded URLs or IPs: npm undici URLs: https://tools.ietf.org/html/rfc7231#section-6.4, https://tools.ietf.org/html/rfc7231#section-6.4.4, 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://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/#enumdef-requestduplex, http://fetch.spec.whatwg.org/#forbidden-method, https://websockets.spec.whatwg.org/#feedback-from-the-protocol, https://datatracker.ietf.org/doc/html/rfc6455#section-7.1.4, https://andreubotella.github.io/multipart-form-data/#multipart-form-data-boundary, https://andreubotella.github.io/multipart-form-data/#multipart-form-data-parser, https://andreubotella.github.io/multipart-form-data/#parse-multipart-form-data-headers, 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, https://www.rfc-editor.org/rfc/rfc7231#section-7.1.1.1, https://www.rfc-editor.org/rfc/rfc6265#section-4.1.1, https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-prefixes-00#section-3.1, https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-prefixes-00#section-3.2, https://html.spec.whatwg.org/multipage/webappapis.html#environment-settings-object, https://html.spec.whatwg.org/multipage/server-sent-events.html#sse-processing-model, 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/#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://github.com/nodejs/undici/issues/2630, https://w3c.github.io/FileAPI/#dom-filereader-readystate, https://w3c.github.io/FileAPI/#dom-filereader-result, https://w3c.github.io/FileAPI/#dom-filereader-empty, https://w3c.github.io/FileAPI/#dom-filereader-loading, https://w3c.github.io/FileAPI/#dom-filereader-done, https://fetch.spec.whatwg.org/#concept-method-normalize, https://dom.spec.whatwg.org/#dom-abortsignal-any, https://github.com/nodejs/undici/issues/1926., https://github.com/nodejs/undici/pull/1910#issuecomment-1464495619., https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry, https://mimesniff.spec.whatwg.org/#parse-a-mime-type, https://mimesniff.spec.whatwg.org/#http-quoted-string-token-code-point, https://fetch.spec.whatwg.org/#data-url-processor, https://fetch.spec.whatwg.org/#data-url-struct, https://url.spec.whatwg.org/#concept-url-serializer, https://infra.spec.whatwg.org/#collect-a-sequence-of-code-points, https://url.spec.whatwg.org/#string-percent-decode, https://url.spec.whatwg.org/#percent-decode, https://mimesniff.spec.whatwg.org/#http-token-code-point, https://mimesniff.spec.whatwg.org/#mime-type, https://mimesniff.spec.whatwg.org/#mime-type-essence, https://fetch.spec.whatwg.org/#http-whitespace, https://infra.spec.whatwg.org/#forgiving-base64-decode, https://fetch.spec.whatwg.org/#collect-an-http-quoted-string, https://fetch.spec.whatwg.org/#example-http-quoted-string, https://mimesniff.spec.whatwg.org/#serialize-a-mime-type, https://infra.spec.whatwg.org/#ascii-whitespace, https://infra.spec.whatwg.org/#strip-leading-and-trailing-ascii-whitespace, https://infra.spec.whatwg.org/#isomorphic-decode, https://mimesniff.spec.whatwg.org/#minimize-a-supported-mime-type, CacheStorage.open, https://datatracker.ietf.org/doc/html/rfc6455#section-6.1, https://datatracker.ietf.org/doc/html/rfc6455#section-5.2, https://fetch.spec.whatwg.org/#body-mixin, https://dom.spec.whatwg.org/#concept-event-fire, https://tools.ietf.org/html/rfc7230#section-6.3.2, https://developer.mozilla.org/en-US/docs/Web/API/Blob, https://developer.mozilla.org/en-US/docs/Web/API/File, https://www.rfc-editor.org/rfc/rfc7230#section-3.3.2, https://github.com/nodejs/undici/issues/258, https://fetch.spec.whatwg.org/#response-create, 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.24.1 ℹ 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.24.1. 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

[guibranco]

Automatically approved by gstraccini[bot]