chore(deps): update dependency azure.resourcemanager.kubernetesconfiguration to 1.2.1

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
Azure.ResourceManager.KubernetesConfiguration (source)	1.2.0 → 1.2.1

---

Release Notes

Azure/azure-sdk-for-net (Azure.ResourceManager.KubernetesConfiguration)

v1.2.1

Compare Source

1.2.1 (2026-04-27)

Features Added

• Enable the new model serialization by using the System.ClientModel, refer this document for more details.
• Exposed JsonModelWriteCore for model serialization procedure.

Other Changes

• Upgraded dependent Azure.Core to 1.54.0.
• Upgraded dependent Azure.ResourceManager to 1.14.0.

---

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.

[claude]

Dependency Update Review: Azure.ResourceManager.KubernetesConfiguration 1.2.0 → 1.2.1

Change: Single-line bump in Directory.Packages.props — clean, minimal, exactly what a PATCH update should look like.

What's in 1.2.1

• Enables new model serialization via System.ClientModel (the JsonModelWriteCore exposure is an additive, non-breaking change)
• Transitive upgrades: Azure.Core → 1.54.0, Azure.ResourceManager → 1.14.0

Assessment

This is a routine PATCH bump from Renovate with high merge confidence. PATCH releases in the Azure SDK for .NET are well-governed — they do not introduce breaking changes, only bug fixes and non-breaking feature additions. The transitive dependency upgrades are also safe: both Azure.Core and Azure.ResourceManager are minor-version changes that follow the same backward-compatibility policy.

The use of central package management (Directory.Packages.props) is the correct pattern for managing version consistency across this solution, and the change is scoped exactly as it should be — no project files needed touching.

No concerns. Approve for merge.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	✅ 0 (≤ 20 complexity)

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.}