chore(deps): update dependency azure.security.keyvault.secrets to 4.11.0

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
Azure.Security.KeyVault.Secrets (source)	4.10.0 → 4.11.0

---

Release Notes

Azure/azure-sdk-for-net (Azure.Security.KeyVault.Secrets)

v4.11.0

Compare Source

4.11.0 (2026-05-05)

Other Changes

• Updated dependency on Azure.Core to 1.54.0, which includes fixes for duplicate schema registration.

---

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]

Code Review

This is a routine Renovate bot dependency update bumping Azure.Security.KeyVault.Secrets from 4.10.0 to 4.11.0 in Directory.Packages.props.

Assessment: Looks good to merge.

A few observations:

Change quality: The single-line change in Directory.Packages.props is exactly what's expected for a Central Package Management (CPM) version bump. No individual project files needed touching, which is the correct pattern for this repo's CPM setup.

Release notes: The 4.11.0 release is a non-breaking "Other Changes" release — the only change is updating the Azure.Core transitive dependency to 1.54.0 (which includes fixes for duplicate schema registration). There are no new APIs, behavior changes, or deprecations to account for.

Version consistency: It's worth noting the three KeyVault packages are now on slightly different versions:

• Azure.Security.KeyVault.Certificates → 4.8.0
• Azure.Security.KeyVault.Keys → 4.9.0
• Azure.Security.KeyVault.Secrets → 4.11.0

This is fine — each package has its own independent release cadence — but if the intent is to keep them in sync, the Certificates and Keys packages may have minor updates available too. Not a blocker.

Auto-merge: Automerge is already enabled on this PR, which is appropriate for low-risk patch/minor bot-generated dependency updates like this one.

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