chore(deps): update actions/upload-artifact action to v7.0.1

[renovate-bot-cbcoutinho]

This PR contains the following updates:

Package	Type	Update	Change
actions/upload-artifact	action	patch	v7.0.0 → v7.0.1

---

Release Notes

actions/upload-artifact (actions/upload-artifact)

v7.0.1

Compare Source

What's Changed

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

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[claude]

PR Review: chore(deps): update actions/upload-artifact action to v7.0.1

Summary: This is a patch-level dependency update from Renovate Bot, bumping actions/upload-artifact from v7.0.0 → v7.0.1.

Assessment: ✅ Looks Good

Security

• The PR correctly uses SHA-pinned references (043fb46d1a93c77aae656e7c1c64a875d1fc6a0a) rather than mutable tags — this is the right approach and protects against supply chain attacks where a tag could be silently repointed.
• The new SHA corresponds to the legitimate v7.0.1 release on the actions/upload-artifact repo.

Changes in v7.0.1
The upstream release notes indicate this is a documentation-only and minor internal dependency update (typespec/ts-http-runtime 0.3.5). No functional changes to the artifact upload behavior, so there is no regression risk.

Code Quality / Best Practices

• Single-line diff, minimal blast radius.
• The if: always() on the upload step is appropriate for capturing test results even on failure — no change needed there.

Verdict: Safe to merge. This is a routine automated maintenance update with no functional impact.