.NET 10.0 RC 1 September 2025 Update - .NET 10.0.0-rc.1 and SDK 10.0.100-rc.1

[dotnet-sb-bot]

.NET 10.0 RC 1 SDKs:

• 10.0.100-rc.1.25451.107:
  • Please use the v10.0.100-rc.1.25451.107 tag to source-build .NET SDK version 10.0.100-rc.1.25451.107.
  • Release Notes: https://github.com/dotnet/core/blob/main/release-notes/10.0/preview/rc1/10.0.0-rc.1.md
  • Tag URL: https://github.com/dotnet/dotnet/releases/tag/v10.0.100-rc.1.25451.107

@dotnet/distro-maintainers

[omajid]

I am trying to build the release using the tarball, but it fails due to branding:

$ ./build.sh --source-only --release-manifest release.json -- /p:UseSystemLibs=+brotli++rapidjson++zlib+-lttng- /p:TargetRid=fedora.42-x64 /p:OfficialBuilder=Fedora /p:MinimalConsoleLogOutput=false /p:ContinueOnPrebuiltBaselineError=true /v:n /p:LogVerbosity=n
NuGet packages cache: '/home/omajid/fedora-git/dotnet10.0/dotnet10.0-10.0.100_rc.1.25451.107-build/dotnet-10.0.100-rc.1.25451.107/.packages/'
ERROR: Failed to find branding in /home/omajid/fedora-git/dotnet10.0/release.json

The release.json file at https://github.com/dotnet/dotnet/releases/tag/v10.0.100-rc.1.25451.107 doesn't include any branding either.

Is rtm the right branding to use?

[corngood]

I added --branding default to build.sh flags, but I'm not sure about the implications, and I haven't finished testing yet.

[dviererbe]

I added --branding preview and it failed, because some files couldn't be found. So don't use that.

[mthalman]

Apologies for this bug. Please pass --branding default to build.sh as a workaround. We'll get this fixed for RC 2.

[mthalman]

#5337

[omajid]

I finished testing with branding --rtm: it doesn't work. --branding default works.