chore(deps): update OData, Cosmos, MongoDB, Swashbuckle and AutoMapper
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 52/100
- Issue-Typ
- Refactoring
- Klarheit
- Klar beschrieben
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- azure, csharp, github-actions, mongodb, postgresql
- Bereich
- backend, build-system, databases
Rechercherichtung
Start with the root Directory.Packages.props and verify the listed package versions on NuGet. Update the five scoped dependencies, then run targeted server, OData, Cosmos, MongoDB, Swashbuckle, and Automapper tests before the full restore, build, and test commands. Check vulnerable packages and NU190x warnings; the work is done when versions, tests, and CI meet the acceptance criteria.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Part 3 of the outdated-package sweep (dotnet-outdated 4.8.1, 2026-11-05). Minor version updates for runtime/library dependencies of the shipped packages. Depends on nothing, but easiest after the "bump .NET, EF Core and library patch versions" PR lands (same file, avoids conflicts).
Scope (this PR only)
Root Directory.Packages.props:
| Package | Current | Target | Used by | Risk / what to check |
|---|---|---|---|---|
Microsoft.AspNetCore.OData |
9.4.1 | 9.5.0 | CommunityToolkit.Datasync.Server |
9.5.0 still depends on OData.Core/Edm/Spatial [8.4.0, 9.0.0), so compatible with the 8.4.x pins. Run server + OData query tests. |
Microsoft.Azure.Cosmos |
3.61.0 | 3.63.3 | Server.CosmosDb |
Run Cosmos tests (need COSMOS_CONNECTION_STRING; otherwise skipped, say so in the PR). |
MongoDB.Driver |
3.9.0 | 3.13.0 | Server.MongoDB |
Four minor versions. Run the MongoDB suite (Testcontainers, Docker required). Skim release notes at https://github.com/mongodb/mongo-csharp-driver/releases for deprecations. |
Swashbuckle.AspNetCore |
10.2.1 | 10.3.1 | Server.Swashbuckle + its tests |
Verify the explicit Microsoft.OpenApi 2.7.5 pin (see XML comment) still resolves and no NU1903 appears; if Swashbuckle now floats a patched OpenApi, the pin may be re-evaluated but leave it unless clearly obsolete. |
AutoMapper |
16.1.1 | 16.3.0 | Server.Automapper |
Run the Automapper tests. Check licensing/notes of 16.3.0 on https://github.com/LuckyPennySoftware/AutoMapper/releases . |
Verify versions on NuGet first (https://api.nuget.org/v3-flatcontainer/<lowercase-id>/index.json); use a newer patch of the same minor if it exists.
Out of scope: test tooling (separate issue), Microsoft.OData.*/Microsoft.Spatial (patch issue / blocked major issue), NSwag.AspNetCore, LiteDB, Azure.Identity (not outdated).
Steps
- Edit props. If a package forces code changes (API deprecations/obsoletions treated as errors), make the minimal fix and note it in the PR; if it needs substantive work, drop that package from this PR and file a follow-up.
dotnet restore && dotnet build && dotnet test(Docker running). Targeted first:dotnet test tests/CommunityToolkit.Datasync.Server.MongoDB.Testetc.dotnet list Datasync.Toolkit.sln package --vulnerable --include-transitivemust be empty; no NU190x warnings on restore.- Dispatch
build-library.ymlon the fork with--ref <branch>.
Acceptance criteria
- All five packages at target versions (or a documented, justified exception).
- Local and CI build/test green.
- PR title:
chore(deps): update OData, Cosmos, MongoDB, Swashbuckle and AutoMapper.
- Vorherrschende Sprache
- C#
- Sterne
- 184
- Forks
- 48
- Ø Merge
- 21 Min.
- Gemergte PRs (30 T.)
- 7
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus CommunityToolkit/Datasync
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
CommunityToolkit/Datasync#600 · 1 Kommentar ·
-
Blocked dependencies Server
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 25/100
CommunityToolkit/Datasync#594 ·
-
dependencies Examples
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 40/100
CommunityToolkit/Datasync#593 ·
-
dependencies Infrastructure
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 72/100
CommunityToolkit/Datasync#592 ·
-
dependencies Infrastructure
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
CommunityToolkit/Datasync#591 ·
Alle Issues in CommunityToolkit/Datasync
Ähnliche Issues
-
enhancement needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
microsoft/microsoft-ui-reactor#1460 ·
Maintainer antworten meist innerhalb von 1 Tag
-
t/bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
dotnet/maui#39950 · 1 Reaktion ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
NimblePros/deviq-hugo#121 ·
Maintainer antworten meist innerhalb von 1 Tag
-
RANDOM_REPLACE does not keep the date format when the month abbreviation has a trailing periodOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
philterd/phileas-dotnet#188 ·
-
enhancement triaged
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
nikneem/sessionize-api-client#55 · 3 Kommentare ·