Repository navigation
Add a net11.0 target to OctoVersion.Core - #399
Merged
Merged
Conversation
.NET 11 shipped on 2026-11-10. Target net11.0 alongside net10.0 in OctoVersion.Core, and run the tests on both. global.json moves to SDK 11.0.100, which is needed to build net11.0, and CI installs the .NET 10 runtime as well. The tool stays on net10.0 but rolls forward to a newer major runtime when .NET 10 isn't installed. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Resolves the RollForward comment conflict with #400 by keeping main's wording. Co-Authored-By: Claude Opus 5.5 <[email protected]>
droyad
approved these changes
Nov 16, 2026
The build project targets net11.0, the net10.0 tests roll forward to the .NET 11 runtime, and the OctoVersion tool used by the build moves to 2.0.7, which rolls forward too. CI no longer installs .NET 10. Co-Authored-By: Claude Opus 5.5 <[email protected]>
# Conflicts: # global.json
Octopus.Nuke.Common 11.0.474 runs on .NET 11 from the apphost, and its dependencies are new enough that the NuGet.Packaging and System.Security.Cryptography.Xml overrides are no longer needed. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of DPT-3862 (Make .NET 11 available on the build platform).
.NET 11 shipped on 2026-11-10 (SDK 11.0.100).
Octopus.OctoVersion.Coretargetsnet11.0alongsidenet10.0, and the tests run on both.net10.0. It now setsRollForward=Major, so it runs on a machine that has only a newer runtime. Where .NET 10 is installed, it still runs on .NET 10. I choseMajoroverLatestMajorso agents that have both keep running it on 10.Cake.OctoVersionstays onnet10.0, the runtime Cake runs on.global.jsonmoves to SDK11.0.100, which is needed to buildnet11.0. CI installs only .NET 11. Thenet10.0tests roll forward to the .NET 11 runtime.net11.0and usesOctopus.Nuke.Commoninstead ofNuke.Common. Nuke 10.1.0 crashes at startup on .NET 11. Octopus.Nuke's dependencies also replace theNuGet.PackagingandSystem.Security.Cryptography.Xmloverrides.global.jsonnow needs SDK 11, so the prettybot job will fail untiltool-resharper-clihas SDK 11 (OctopusDeploy/tool-containers#334).This is a draft until we decide we want
net11.0assets in the packages. .NET 11 is a short-term release, but its support ends on 2028-11-14, the same day as .NET 10.🤖 Generated with Claude Code