chore(deps): bump @actions/artifact from 2.3.2 to 6.2.1

[dependabot]

Bumps @actions/artifact from 2.3.2 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

4.0.0

• Add support for Node 24 #2110
• Fix: artifact pagination bugs and configurable artifact count limits #2165
• Fix: reject the promise on timeout #2124
• Update dependency versions

2.3.3

• Dependency updates #2049

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/artifact 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)