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

未关闭
#589 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
重构
描述清晰度
描述清楚
活跃度
活跃
技术栈
azure, csharp, github-actions, mongodb, postgresql

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
C#
星标
184
派生
48
平均合并
21 分钟
30 天内合并 PR
7

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CommunityToolkit/Datasync 的其他 Issue

查看 CommunityToolkit/Datasync 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。