chore(deps): update aws-sdk-net monorepo

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
AWSSDK.Lambda	4.0.13.8 → 4.0.14.1
AWSSDK.S3	4.0.20.1 → 4.0.21.1

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Renovate Bot.

[claude]

This is a routine Renovate-generated patch update bumping two AWS SDK NuGet packages:

• AWSSDK.Lambda: 4.0.13.8 → 4.0.13.10
• AWSSDK.S3: 4.0.20.1 → 4.0.20.3

Both changes are isolated to Directory.Packages.props using the centralized package management pattern, which is the correct approach for this repository — no individual .csproj files need to be touched.

Observations:

• These are patch-level bumps within the same minor version, carrying low risk.
• Automerge is already configured, which is appropriate for dependency PRs of this nature.
• No API surface changes are expected at this version delta; both packages follow standard semver conventions.
• The centralized Directory.Packages.props approach means all consuming projects in the solution will pick up the update consistently, avoiding version drift across projects.

No concerns with this change. Safe to 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

_{TIP This summary will be updated as you push new changes. Give us feedback}

[claude]

This is a routine dependency update generated by Renovate Bot, bumping two AWS SDK packages:

• AWSSDK.Lambda: 4.0.13.8 → 4.0.13.10 (patch)
• AWSSDK.S3: 4.0.20.1 → 4.0.20.4 (patch)

Both are patch-level updates within the same minor version series, which typically contain bug fixes and minor improvements with no breaking changes. The change is limited to a single file (Directory.Packages.props), which is the correct centralized package management approach for this repo.

No architectural or design concerns. The change is minimal, well-scoped, and follows the established pattern of managing dependency versions centrally. Auto-merge is appropriate for patch-level dependency updates of this nature.

[claude]

This is a routine Renovate-generated patch dependency update bumping two AWS SDK NuGet packages:

• AWSSDK.Lambda: 4.0.13.8 -> 4.0.13.11 (patch, 3 releases)
• AWSSDK.S3: 4.0.20.1 -> 4.0.20.4 (patch, 3 releases)

Previous review notes addressed: The prior review comments noted these are safe patch-level bumps. The current diff confirms the same low-risk nature — the versions have advanced slightly further (to .11 and .4 respectively, vs .10 and .3 at the time of the previous reviews), but the characterization remains the same.

Assessment:

• Change is correctly isolated to Directory.Packages.props, the centralized version management file — no .csproj files need to be touched, and all consuming projects will pick up the update consistently.
• Patch-level updates in the AWS SDK for .NET typically contain bug fixes, performance improvements, and service API additions, with no breaking changes.
• Automerge is already enabled, which is the appropriate strategy for dependency PRs of this nature.
• Codacy reports 0 new issues, as expected for a version-only change.

No concerns. Safe to merge.

[claude]

Code Review

This is a routine automated dependency update from Renovate Bot, bumping two AWS SDK packages in Directory.Packages.props:

• AWSSDK.Lambda: 4.0.13.8 → 4.0.14
• AWSSDK.S3: 4.0.20.1 → 4.0.21

Assessment: No issues found.

The change is minimal and correct — both version bumps are PATCH-level updates within the same major version (4.x), so no breaking API changes are expected. The centralized package version management via Directory.Packages.props is the right pattern for a multi-project solution like this.

A few observations:

• The Codacy static analysis bot reports 0 new issues, which is expected for a version-only change.
• Auto-merge is enabled and appropriate for dependency updates of this nature.
• No code logic or test changes are involved, so no behavioral regression risk.

This PR is safe to merge.