Hi all,
Flagging a date that is now close: .NET 8 reaches end of support on 10 November 2026, roughly three months from now. After that Microsoft stops shipping security and reliability patches for the runtime, the ASP.NET Core shared framework, and the mcr.microsoft.com/dotnet/aspnet:8.0 container images.
The backend currently targets net8.0 in Origam.Server, Origam.Architect.Server, Origam.Composer, OrigamScheduler and a few smaller projects, and the Docker images build on the 8.0 runtime base.
Why this looks worth putting on the roadmap now rather than later:
- .NET 10 is the LTS successor. Released November 2025, supported until November 2028 - a full three-year window rather than another short hop.
- There is no intermediate step. .NET 9 was an STS release and went out of support in May 2026, so 8 to 10 is the only supported path.
- The published container images stop being patched. Anyone deploying the official ORIGAM images after November would be running an unpatched runtime, and CVE scanners in customer environments will pick that up. For an enterprise-facing product that tends to become someone’s compliance problem fairly quickly.
- The work is not confined to the
.csprojfiles. The SDK is pinned inbackend/global.json, the GitHub workflows and the Azure build pipelines reference 8.0 explicitly, the Dockerfiles pin the 8.0 base images, andTreatWarningsAsErrorsis on repo-wide - so a newer compiler surfacing new warnings turns straight into build failures. That is the kind of change that wants lead time and a quiet window rather than a scramble in late October. - The library layer is largely out of the way. Most of the codebase is
netstandard2.0and unaffected; only the handful of executable and web projects carry anet8.0target, which keeps the scope smaller than it might first appear.
Not proposing an approach here, just raising the date while there is still room to plan around it. Is a .NET 10 move already on the roadmap for one of the upcoming releases?
Thanks!