Skip to content

[GFX-550] build(dotnet): 升级构建目标至 .NET 10 并同步 global.json 与发布 CI - #20

Merged
AlianBlank merged 2 commits into
mainfrom
feature/GFX-550
Aug 6, 2026
Merged

[GFX-550] build(dotnet): 升级构建目标至 .NET 10 并同步 global.json 与发布 CI#20
AlianBlank merged 2 commits into
mainfrom
feature/GFX-550

Conversation

@AlianBlank

Copy link
Copy Markdown
Collaborator

背景

同步上游 .NET 10 构建目标(上游 commit 84bace04,net10 kerryjiang#827)。

本仓结构与上游不同(单目标 TargetFrameworkLangVersion=10.0、无 global.json、CI 为 publish-nuget.yml),故按本仓风格做等效同步,而非 1:1 套用上游 diff。

改动(3 文件)

  • Directory.Build.propsTargetFramework net8.0net10.0(保持单目标风格,LangVersion=10.0 不变)。
  • 新增 global.jsonsdk.version=10.0.0rollForward=latestFeature(与上游一致)。
  • .github/workflows/publish-nuget.ymldotnet-version 8.0.x10.0.xsetup-dotnet@v1@v4(TFM 升至 net10.0 后,原 CI 只装 .NET 8 SDK 且 v1 早于 .NET 10 发布,会导致 publish 构建失败,故配套升级)。

验证

  • dotnet build GameFrameX.SuperSocket.sln(Debug):0 Error(234 Warning 均为既有 CS1591 缺失 XML 文档注释 + 1 NU1510,与本次升级无关)。
  • dotnet build GameFrameX.SuperSocket.sln -c Release0 Error
  • global.json 生效:dotnet --version → 10.0.201。
  • 产物核验:程序集输出到 bin/app/net10.0/;生成的 nupkg 内 nuspec 依赖组 targetFramework=net10.0

Linear: GFX-550

同步上游 commit 84bace0 (net10 kerryjiang#827)。Directory.Build.props: TargetFramework net8.0 → net10.0(保持单目标风格,LangVersion 不变);新增 global.json(sdk.version=10.0.0, rollForward=latestFeature);publish-nuget.yml: setup-dotnet@v1 → @v4, dotnet-version 8.0.x → 10.0.x(TFM 升级后 CI 必要配套)。

Linear: GFX-550
@linear-code

linear-code Bot commented Aug 5, 2026

Copy link
Copy Markdown

GFX-550

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@AlianBlank, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8c11be3c-8473-44db-95fb-525b04b81525

📥 Commits

Reviewing files that changed from the base of the PR and between 7187938 and 5b3d10b.

📒 Files selected for processing (3)
  • .github/workflows/publish-nuget.yml
  • Directory.Build.props
  • global.json

Comment @coderabbitai help to get the list of available commands.

@AlianBlank
AlianBlank merged commit eaf0a65 into main Aug 6, 2026
3 checks passed
@AlianBlank
AlianBlank deleted the feature/GFX-550 branch August 6, 2026 03:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant