[Tracking] Move to .NET 11

未关闭
  • 哪里不对？
#372 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
csharp, docker, openapi
领域
backend-api-design, devops

调研方向

This is a tracking issue, not a groomed story, and work is blocked until Microsoft.AspNetCore.OpenApi 11.0.0 is stable. When unblocked, start by grooming the framework step for TaskFlow.Api and TaskFlow.Api.Tests, then check the workflows, API Dockerfile, and the OpenAPI generation command (npm run gen:api). Done means the framework, CI/Docker, generated client and spec, migrations, and real-SQLite tests have been checked as described.

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

描述

blocked dependencies

Groups the work for moving TaskFlow from .NET 10 to .NET 11. This is a place to collect the pieces, not a groomed story. Blocked until Microsoft.AspNetCore.OpenApi 11.0.0 is stable (as of 2026-10-30 NuGet has 11.0.0-rc.3.26522.148 and no stable 11.0.0). When it ships, groom the framework step below before starting.

Sub-issues

  • #301 — Upgrade Microsoft.OpenApi to 3.x (3.5.4 or later) and remove the Dependabot ignore and the pin comment
  • #165 — Upgrade Asp.Versioning.Mvc, .ApiExplorer and add Asp.Versioning.OpenApi. Held: Asp.Versioning.OpenApi 10.2.3 depends on Microsoft.OpenApi [2.7.5, 3.0.0), which blocks #301 until Asp.Versioning ships a release that accepts Microsoft.OpenApi 3.x

Not yet issues (to groom when .NET 11 is stable)

  • Framework step: TargetFramework and MicrosoftPlatformVersion in TaskFlow.Api and TaskFlow.Api.Tests, EF Core 11 and its provider packages, Microsoft.Extensions.* and OpenTelemetry package compatibility
  • CI and Docker: .NET SDK version in the workflows, the API Dockerfile base images, and the Dependabot docker block
  • Regenerate the OpenAPI spec and the web client (npm run gen:api) and check the output is unchanged or intentionally changed
  • Check migrations still apply on startup and the real-SQLite tests still pass

Suggested order

  1. Wait for stable Microsoft.AspNetCore.OpenApi 11.0.0.
  2. Check whether an Asp.Versioning.* release supports Microsoft.OpenApi 3.x. If so, #165 can go before or with #301. If not, #165 stays held and #301 cannot use an Asp.Versioning.OpenApi 10.x.
  3. Framework step, then #301.

Notes

  • Asp.Versioning.Mvc 10.2.1 targets net10.0 only (nuspec, checked 2026-10-30). Whether its net10.0 assets work on net11.0 is part of step 2.
  • #284 (TypeScript 7) is independent of this move and is gated on a typescript-eslint release, not on .NET.
主要语言
C#
星标
1
派生
0
平均合并
2 小时 2 分钟
30 天内合并 PR
98

环境准备

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

从这里开始

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

nevridge/TaskFlow 的其他 Issue

查看 nevridge/TaskFlow 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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