chore(deps): update dependency dotnet-sdk to v10.0.302

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
dotnet-sdk	dotnet-sdk	patch	10.0.301 → 10.0.302

---

Release Notes

dotnet/sdk (dotnet-sdk)

v10.0.302

Compare Source

---

Configuration

📅 Schedule: (UTC)

• 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 Mend Renovate.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e29184a2e0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Revert to a released .NET SDK version

This pins the repo to SDK 10.0.302, but the official .NET download page currently lists 10.0.301 as the available .NET 10 SDK (released June 9, 2026: https://dotnet.microsoft.com/download). In any checkout or GitHub workflow that only installs the released 10.0.x SDK, global.json asks dotnet for a higher patch than exists, so restore/build/test commands will fail before reaching the project code.

Useful? React with 👍 / 👎.

[claude]

Review

Overview: Automated Renovate PR bumping the pinned .NET SDK version in global.json from 10.0.301 to 10.0.302 (patch release). Single line changed, no source code affected.

Analysis:

• Change is minimal and mechanical — just the sdk.version field in global.json.
• rollForward: "latestMajor" and allowPrerelease: true are unchanged, so behavior otherwise stays the same; this only tightens the pinned floor version.
• No source-generator, reflection-engine, or public API changes — dual-mode and snapshot-testing rules don't apply here.
• No test coverage concerns since there's no code logic change; CI building/testing against the new SDK patch is the effective validation.

Risks: Low risk. Worth confirming CI passes (build + test suite) against SDK 10.0.302 before merging, particularly given this repo multi-targets net8.0;net9.0;net10.0 — patch SDK bumps have occasionally shifted analyzer/source-generator behavior in .NET history, so a green CI run is the right signal here rather than manual review.

Verdict: LGTM pending green CI. No code quality, correctness, or security issues to flag.

[claude]

Review

Overview: Automated Renovate PR bumping the pinned .NET SDK version in global.json from 10.0.301 to 10.0.302 (patch release). Single line changed (+1/-1), no source, test, or public API changes.

Analysis:

• Purely mechanical sdk.version bump; rollForward: "latestMajor" and allowPrerelease: true are untouched, so fallback/pre-release behavior is unaffected.
• No source-generator or reflection-engine code touched, so the dual-mode and snapshot-testing rules don't apply here.
• No architectural or design concerns apply to a config-only dependency bump — there's no code shape to critique.
• Matches the prior automated review on this PR; nothing new to flag since that pass — the diff and commit are unchanged.

CI status: Analyze (actions), integration-tests, modularpipeline (de-DE), Codacy, and security/snyk are green. modularpipeline for ubuntu/macos/windows/fr-FR/pl-PL and Analyze (csharp) are still pending at review time — worth confirming those finish green before merge, since a patch SDK bump can occasionally shift source-generator/analyzer output across the net8.0;net9.0;net10.0 multi-target matrix.

Verdict: LGTM pending the remaining CI legs going green. No code quality, correctness, or security issues to flag.