chore(actions): bump actions/upload-artifact from 4.6.2 to 7.0.1

[dependabot]

Bumps actions/upload-artifact from 4.6.2 to 7.0.1.

Release notes

Sourced from actions/upload-artifact's releases.

v7.0.1

What's Changed

• Update the readme with direct upload details by @​danwkennedy in actions/upload-artifact#795
• Readme: bump all the example versions to v7 by @​danwkennedy in actions/upload-artifact#796
• Include changes in typespec/ts-http-runtime 0.3.5 by @​yacaovsnc in actions/upload-artifact#797

Full Changelog: actions/upload-artifact@v7...v7.0.1

v7.0.0

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

• Add proxy integration test by @​Link- in actions/upload-artifact#754
• Upgrade the module to ESM and bump dependencies by @​danwkennedy in actions/upload-artifact#762
• Support direct file uploads by @​danwkennedy in actions/upload-artifact#764

New Contributors

• @​Link- made their first contribution in actions/upload-artifact#754

Full Changelog: actions/upload-artifact@v6...v7.0.0

v6.0.0

v6 - What's new

[!IMPORTANT] actions/upload-artifact@v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

• Upload Artifact Node 24 support by @​salmanmkc in actions/upload-artifact#719
• fix: update @​actions/artifact for Node.js 24 punycode deprecation by @​salmanmkc in actions/upload-artifact#744
• prepare release v6.0.0 for Node.js 24 support by @​salmanmkc in actions/upload-artifact#745

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

v5.0.0

What's Changed

... (truncated)

Commits

• 043fb46 Merge pull request #797 from actions/yacaovsnc/update-dependency
• 634250c Include changes in typespec/ts-http-runtime 0.3.5
• e454baa Readme: bump all the example versions to v7 (#796)
• 74fad66 Update the readme with direct upload details (#795)
• bbbca2d Support direct file uploads (#764)
• 589182c Upgrade the module to ESM and bump dependencies (#762)
• 47309c9 Merge pull request #754 from actions/Link-/add-proxy-integration-tests
• 02a8460 Add proxy integration test
• b7c566a Merge pull request #745 from actions/upload-artifact-v6-release
• e516bc8 docs: correct description of Node.js 24 support in README
• Additional commits viewable in compare view

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)

Brida maintainer release classification

• release-impact: none
• release-note: Update the GitHub-owned upload-artifact action in finalize-release to the reviewed v7.0.1 immutable SHA (043fb46d); no SDK runtime or npm package surface changes.
• qa-scope: Required Node 22, Node 24, public-surface validate, trusted-base Release and QA metadata policy, CodeQL and full-SHA Actions policy; next finalize-release run must upload and download exactly one verified npm tarball by artifact name.

[0xnavarro]

Triage (2026-10-01): the Release and QA metadata failure was caused by Dependabot PR bodies not including the required release-impact / release-note / qa-scope lines (scripts/check-pr-metadata.mjs). I fixed it the same way the maintainer did for #35, by appending a Brida maintainer release classification block (release-impact: none, since this only touches the release workflow and not the npm surface). The check now passes and the PR is CLEAN. The policy itself was not weakened.

I verified that the pinned SHA matches the upstream tag via gh api repos/actions/*/commits/<tag>.

Needs a maintainer to:

• approve the major bump. upload-artifact v4→v7 and download-artifact v4→v8 add ESM, a Node 24 runtime, and download-artifact v8 now errors on hash mismatch by default. The workflow uploads/downloads a single named artifact, which is unaffected by the v5 by-ID path change. Merge chore(actions): bump actions/upload-artifact from 4.6.2 to 7.0.1 #50 and chore(actions): bump actions/download-artifact from 4.3.0 to 8.0.1 #51 together so the release pipeline is upgraded as a pair.
• choose the merge method. This repo is rebase-only (allow_merge_commit=false, linear history), but the org rule requires merge commits.

[dependabot]

Superseded by #55.