chore: exploratory migration to .NET 10

[shukebeta]

Goal

Explore upgrading the solution from net8.0 to net10.0. This is not a sprint item — the branch should be kept in sync with master and merged only when all blockers are resolved and CI is fully green.

Branch strategy

Work on a dedicated branch (e.g. chore/net10-migration). Rebase or merge from master regularly. Do not open a PR to master until every item in the checklist below is resolved.

Known blockers

1. Shukebeta.Api.Framework — highest priority

• The private NuGet package currently targets net8.0 only.
• Must be updated to target net10.0 (or netstandard2.1 / multi-target) before anything else compiles.
• WeihanLi.Common 1.0.64 is a transitive dependency of this package — verify it supports net10 as well.

2. Telegram.Bot 18.0.0

• Only declares targets up to .NETCoreApp3.1.
• Upgrade to v19+ which has explicit net8/net9 support. Review breaking-change log between v18 and v19 before upgrading.

3. SqlSugarCore 5.1.4.189

• Targets netstandard2.1 only; no explicit net10 target.
• Likely works via compatibility shim but ORM runtime reflection behaviour may differ. Run the full integration test suite after the upgrade and watch for subtle query/mapping regressions.

Items to verify (probably fine, but confirm)

Package	Current version	Concern
Mastonet	3.1.2	Declared support stops at net8; run Mastodon integration tests
CoreHtmlToImage	1.0.6	netstandard2.0 — net10 stricter runtime validation may surface issues
AutoMapper	13.0.1	Known high-severity vulnerability (GHSA-rvv3-g6hj-g44x); consider upgrading alongside the migration

Migration steps (suggested order)

• Update Shukebeta.Api.Framework to support net10; publish new version
• Change global.json SDK version to 10.0.x
• Change all <TargetFramework>net8.0</TargetFramework> → net10.0 in every .csproj
• Resolve compilation errors
• Upgrade Telegram.Bot to v19+ and adapt call sites to breaking changes
• Run dotnet test (unit + integration) and fix failures
• Deploy to a staging environment; smoke-test Telegram and Mastodon sync paths
• Remove dotnet-sdk-8.0 from dev machines and CI once green
• Open PR to master

Runtime note

The production server needs dotnet-runtime-10.0 installed before the first net10 deployment. Install it in parallel with dev work so it is ready when the branch lands.

[shukebeta]

Migration landed on master (f4b1cfa)

The net8 → net10 migration is merged. Summary of what was done and the deviations from the original plan.

Frameworks & SDK

• global.json SDK pinned to 10.0.301
• All projects retargeted net8.0 → net10.0
• Shukebeta.Api.Framework 1.0.0 → 2.0.0 (net10). CustomException<T> is now factory-only (CustomExceptionHelper.New); tests adapted.

Package upgrades & breaking changes

• Telegram.Bot 18.0.0 → 22.10.1: InputOnlineFile removed (InputFile.FromStream), async-suffix methods renamed, Message.MessageId is read-only → ITelegramService now returns int instead of Message.
• AutoMapper: ⚠️ deviation from the plan. The plan suggested upgrading, but AutoMapper 15.x dropped the MIT license (commercial/non-commercial). Pinned to 12.0.1 (last MIT) to match NewWords.Api and stay free for commercial use. This required re-adding AutoMapper.Extensions.Microsoft.DependencyInjection 12.0.1 (the DI extension was a separate package before v13).
• Swashbuckle 6.5 → 10.2.1 (pulls Microsoft.OpenApi 2.x): .Models namespace gone, OpenApiSecuritySchemeReference, AddSecurityRequirement takes a Func<>.
• Microsoft.AspNetCore.* / IdentityModel / NLog bumped to net10-compatible versions; removed unused Microsoft.AspNetCore.OpenApi.
• Fixed a JsonSerializer.Deserialize ambiguity surfaced by new RedisValue implicit conversions in .NET 10.

CI / deploy

• ci.yml / pr-check.yml runners bumped to 10.0.x.
• Staging deploy switched from self-hosted runner to SSH (ubuntu-latest → SSH into the arm host). Framework-dependent publish (host has the runtime), user-level systemd preserved (rootless). Verified working.

Status

• ✅ All 235 unit tests green; build clean.
• ✅ Staging SSH deploy verified.
• ⏳ Not done: production / production-test still run on self-hosted runners with the old config. The racknerd production host needs dotnet-runtime-10.0 before its first net10 deploy, and those two workflows still need migrating (or at least the 8.0.x → 10.0.x bump). Tracking remains open for that.

Closing the migration itself; production cutover is the only remaining item.