.NET 10.0 RC 2 October 2025 Update - .NET 10.0.0-rc.2 and SDK 10.0.100-rc.2

[dotnet-sb-bot]

.NET 10.0 RC 2 SDKs:

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

@dotnet/distro-maintainers

[corngood]

This seems to be the first release published by dotnet-sb-bot, and it no longer has a signature for the github tarballs.

The signature file is still listed under 'assets' in the release json, so we can use that url:

https://github.com/dotnet/dotnet/releases/download/v10.0.100-rc.2.25502.107/dotnet-source-10.0.100-rc.2.25502.107.tar.gz.sig

However, the tarball url no longer seems to be anywhere in the structured json. I guess I'll have to do something like:

https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-$(jq -er .sdkVersion release.json).tar.gz

This feels messier than before. @dotnet/distro-maintainers anyone come up with a better way?

[mthalman]

Yes, we're aware of the issue. For now, target the builds.dotnet.microsoft.com location instead of downloading the sources tarball produced by GitHub. We'll get this resolved for next release.

[corngood]

Also, these new tarballs don't have a root directory in them, which is going to be another special case.

[corngood]

This became too annoying to work around (supporting both types of tarballs), so I'm just disabling the signature check in nixpkgs until this settles.

[omajid]

I was hoping that the two sets of tarballs - official vs github's - would be bit-by-bit identical, specially given we fixed it some time ago: #4290

[corngood]

I opened an issue for this #5369

[corngood]

The release.json now doesn't have a trailing newline, which blows up the nixpkgs linter. Every other one up to this point seems to have had it.

[corngood]

#5368