chore(deps): update OData, Cosmos, MongoDB, Swashbuckle and AutoMapper

Abierto
#589 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
azure, csharp, github-actions, mongodb, postgresql

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

dependencies Server

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

  1. 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.
  2. dotnet restore && dotnet build && dotnet test (Docker running). Targeted first: dotnet test tests/CommunityToolkit.Datasync.Server.MongoDB.Test etc.
  3. dotnet list Datasync.Toolkit.sln package --vulnerable --include-transitive must be empty; no NU190x warnings on restore.
  4. Dispatch build-library.yml on 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.
Lenguaje dominante
C#
Estrellas
184
Forks
48
Merge medio
21 min
PR fusionados (30 d)
7

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CommunityToolkit/Datasync

Todos los issues de CommunityToolkit/Datasync

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.