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

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
actions/upload-artifact	action	major	v6 → v7

---

Release Notes

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

v7

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

[claude]

Code Review

This is a straightforward Renovate Bot dependency update bumping actions/upload-artifact from v6 to v7 in .github/workflows/dotnet.yml.

Change summary: Single line update to the GitHub Action used to upload hang dump artifacts when the CI workflow fails (if: always()).

Assessment: The change looks correct and appropriate. Updating to the latest major version of actions/upload-artifact is a routine maintenance task. The action is used conservatively — only for hang dump collection during failures — so the blast radius of any potential breaking change is limited to CI diagnostics, not the core build or test pipeline.

One point worth being aware of: major version bumps in GitHub Actions (e.g., v3→v4, v4→v5) have historically introduced breaking changes such as deprecations in the artifact API or changes in retention defaults. If hang dump uploads start failing silently after this merges, it would be worth verifying the action inputs (particularly name and path) are still valid for v7. That said, for this particular use case (simple name + glob path), v7 is unlikely to require any input changes.

No issues found. Safe to merge.

[claude]

Code Review

This is a Renovate Bot dependency update bumping actions/upload-artifact from v6 → v7 in .github/workflows/dotnet.yml.

Previous review check: A prior review flagged this as safe, advising to monitor hang dump uploads post-merge in case v7 introduced input API changes. No concerns were raised that required action before merging.

Current state: The diff is a single-line version bump, unchanged from the original PR. CodeFactor and Snyk checks are passing. CI pipeline checks are still pending.

Assessment: The change remains correct and safe. The action is used only for hang dump artifact uploads on CI failure, so the scope of any regression would be limited to diagnostic artifact collection rather than the core build or test pipeline. No breaking input changes are expected for this straightforward usage (simple name + path glob).

No issues found. Safe to merge once CI checks pass.