Skip to content

Update version prefix from 10.0.0 to 11.0.0#16095

Merged
akoeplinger merged 2 commits intomainfrom
akoeplinger-patch-2
Sep 2, 2025
Merged

Update version prefix from 10.0.0 to 11.0.0#16095
akoeplinger merged 2 commits intomainfrom
akoeplinger-patch-2

Conversation

@akoeplinger
Copy link
Copy Markdown
Member

To double check:

Copy link
Copy Markdown
Member

@ViktorHofer ViktorHofer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but we were planning to do a centralized branding update via the VMR.

@akoeplinger
Copy link
Copy Markdown
Member Author

ok, but I already bumped emsdk :D
want me to close this?

@ViktorHofer
Copy link
Copy Markdown
Member

No need to close this one. Just consider doing the other ones from the VMR.

@akoeplinger akoeplinger merged commit 9fc79e0 into main Sep 2, 2025
10 checks passed
@akoeplinger akoeplinger deleted the akoeplinger-patch-2 branch September 2, 2025 09:31
@T-Gro
Copy link
Copy Markdown
Member

T-Gro commented Sep 26, 2025

@akoeplinger , @ViktorHofer :
(aopologies for me not understanding this fully, but I want to be safe).

F# takes Arcade's latest to it's main, which includes this change. Notable the sbom bump from 10 to 11 ( https://github.com/dotnet/arcade/blame/432dff2f163e6a5fdb3c9052c2e58c4ab8c0e2c4/eng/common/core-templates/steps/generate-sbom.yml#L8 ).

Which flows to F# via https://github.com/dotnet/fsharp/pull/18869/files and I feel like we should not accept it yet, since our main still flows into net10.

Is my thinking correct that we should only take this in for net11, i.e. not yet while main is net10 ?

@ViktorHofer
Copy link
Copy Markdown
Member

@T-Gro Arcade main intentionally already targets the .NET 11 release. If fsharp should stay on Arcade 10 for now, update the subscription to point to the ".NET 10 Eng" channel.

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.

3 participants