Distro partners need official build ID for .NET 10 early handoffs

[mthalman]

For .NET 10, you need to know the official build ID to pass in to the build script. For the public release, this is provided in the release.json file attached to the GitHub release. But for early handoffs to distro partners, no such file is provided. And the value is not provided in any other context either.

[ellahathaway]

The release.json file is included in the source tarball for early handoff. I've confirmed that it was included in the latest handoff and that it contains the build ID. Closing.

[MichaelSimons]

Should this be documented? Is this the right UX? It feels weird for git consumers to have to also depend on the source tarball.

[ellahathaway]

As a clarification, the release.json file is bundled in the universal package that we include in the handoff to our partners. It gets coupled in this package alongside the source and detached source signature. The build ID can be found in the release.json file under officialBuildId.

The long-term follow-up will likely include removing the release.json from the universal package as part of https://github.com/dotnet/release/issues/1405 and including via a link to blob storage in the wiki.