chore(deps): bump undici, @actions/artifact and @actions/http-client

[dependabot]

Bumps undici to 6.28.0 and updates ancestor dependencies undici, @actions/artifact and @actions/http-client. These dependencies need to be updated together.

Updates undici from 6.27.0 to 6.28.0

Release notes

Sourced from undici's releases.

v6.28.0

⚠️ Security fixes

• GHSA-m8rv-5g2x-5cg5: a malicious type property on a duck-typed blob-like HTTP/1.1 request body could inject CRLF sequences into the generated content-type header. Undici now coerces and validates the value before adding it to the request. Fixed by 740a0b7c.
• GHSA-8xcm-r25x-g524: the retry interceptor could expose a stale Content-Length after resuming a partial response, potentially causing downstream response desynchronization, hangs, or corruption. Undici now rejects partial responses whose Content-Length is inconsistent with Content-Range. Fixed by cba3a52a, with corrected fixtures in 4fd5a0c6.
• GHSA-v3r7-h72x-cjcm: unsanitized domain and unparsed values passed to setCookie() could inject cookie attributes. Undici now validates cookie domains, paths, and unparsed attributes more strictly. Fixed by af748404.

GHSA-4cwx-7wf7-3272 and GHSA-jr45-8vmc-qm54 affect the cache interceptor in Undici v7 and v8; Undici v6 is not in their affected version ranges.

Full Changelog: nodejs/undici@v6.27.0...v6.28.0

Commits

• 01a912e Bumped v6.28.0 (#5591)
• 481ecfc Use Node 22 and npm 11 to release
• 740a0b7 fix: validate blob body content type
• 2698e49 fix: validate coerced header values for CRLF (#5579)
• 4fd5a0c test(retry): correct broken content-range fixtures in retry-handler.js
• cba3a52 fix(retry): reject partial content length mismatch
• af74840 fix: harden cookie domain, path, and unparsed attribute validation
• See full diff in compare view

Updates @actions/artifact from 4.0.0 to 6.2.1

Changelog

Sourced from @​actions/artifact's changelog.

6.2.1

• Support the RFC 5987 filename* field in the content-disposition header. This allows us to correctly download files and artifacts with Chinese/Japanese/Korean (among other) characters in their name.

6.2.0

• Support uploading single un-archived files (not zipped). Direct uploads are only supported for artifacts version 7+ (based on the major version of actions/upload-artifact). Callers must pass the skipArchive option to uploadArtifact. Only single files can be uploaded at a time right now. Default behavior should remain unchanged if skipArchive = false. When skipArchive = true, the name of the file is used as the name of the artifact for consistency with the downloads: you upload artifact.txt, you download artifact.txt.

6.1.0

• Support downloading non-zip artifacts. Zipped artifacts will be decompressed automatically (with an optional override). Un-zipped artifacts will be downloaded as-is.

6.0.0

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

5.0.3

• Bump @actions/http-client to 3.0.2

5.0.1

• Fix Node.js 24 punycode deprecation warning by updating @azure/storage-blob from ^12.15.0 to ^12.29.1 #2211
• Removed direct @azure/core-http dependency (now uses @azure/core-rest-pipeline via storage-blob)

5.0.0

• Dependency updates for Node.js 24 runtime support
• Update @actions/core to v2
• Update @actions/http-client to v3

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​actions/artifact since your current version.

Updates @actions/http-client from 2.2.1 to 2.2.3

Changelog

Sourced from @​actions/http-client's changelog.

2.2.3

• Fixed an issue where proxy username and password were not handled correctly #1799

2.2.2

• Better handling of url encoded usernames and passwords in proxy config #1782

Commits

• See full diff in compare view

[dependabot]

Looks like these dependencies are up-to-date now, so this is no longer needed.