chore(deps): update dependency npgsql to 10.0.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Npgsql	nuget	patch	10.0.1 → 10.0.2

---

Release Notes

npgsql/npgsql (Npgsql)

v10.0.2

v10.0.2 contains several minor bug fixes.

Milestone issues

Full Changelog: npgsql/npgsql@v10.0.1...v10.0.2

---

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

PR: chore(deps): update dependency npgsql to 10.0.2
Type: Automated dependency update (Renovate Bot) — patch version bump

---

Summary

This is a straightforward patch update from Npgsql 10.0.1 → 10.0.2, which contains minor bug fixes. The change itself is low-risk and appropriate.

---

Observation: Duplicate Version Specification

This PR updates two files:

1. Directory.Packages.props — the centralized package version source
2. examples/CloudShop/CloudShop.Tests/CloudShop.Tests.csproj — also specifies Version="10.0.2" directly on the PackageReference

When Central Package Management (CPM) is enabled via Directory.Packages.props, project files should reference packages without a Version attribute — the version is resolved centrally. Having a Version attribute on a PackageReference alongside a PackageVersion entry in Directory.Packages.props is either redundant (if CPM overrides it) or inconsistent (if this project opts out of CPM).

Recommended approach: Remove the Version attribute from the PackageReference in CloudShop.Tests.csproj and rely solely on Directory.Packages.props:

<!-- Before -->
<PackageReference Include="Npgsql" Version="10.0.2" />

<!-- After (with CPM) -->
<PackageReference Include="Npgsql" />

This is a pre-existing issue that this PR didn't introduce — Renovate Bot is simply maintaining the status quo. However, it's worth addressing in a follow-up to avoid divergence if the central version and the project-level override ever get out of sync (which would be a silent, confusing bug).

---

Verdict

The update itself is correct and safe to merge. The dual-version issue is a pre-existing architectural concern worth a follow-up cleanup, not a blocker for this PR.