Isolated .NET SDK v0.2.0
Released October 2, 2026.
v0.2.0 is the first stable release published under the checksum-verifying stable-release policy. It strengthened SDK and tool acquisition integrity, made installation transactional, expanded the interactive workflow, and added clearer installed-SDK inventory and health checks.
Highlights
- Verified stable release scripts — pinned stable installation verifies the selected PowerShell or Bash script against the release’s deterministic
SHA256SUMSbefore execution. - Verified SDK payloads — installation resolves the exact platform archive from Microsoft’s release metadata and verifies its published SHA-512 before extraction.
- Transactional installation — SDKs are downloaded and extracted into operation-owned staging, exact-version verified, and only then promoted into the isolated SDK root.
- Persistent interactive workflow — interactive mode supports repeated operations with Main, Back, global Exit, manual exact-version entry, compact SDK version lists, and access to older servicing versions on demand.
- Improved inventory and health checks — List separates tool-managed Isolated SDKs from read-only System SDKs, and Verify performs a read-only exact-version health check of an installed isolated SDK.
- Stronger cross-platform validation — Pester and Bats-core behavioral coverage, static analysis, integrity checks, and real end-to-end validation cover the supported Windows/PowerShell, Linux/Bash, and macOS/Bash mappings.
- Expanded operational documentation — release/bootstrap policy, supply-chain trust boundaries, filesystem safety, behavioral parity, project/editor usage, interactive behavior, and validation are documented in the project site.
Integrity and release model
The SHA256SUMS asset verifies consistency between the selected tagged tool script and the checksum material published with the same GitHub Release. This is an integrity check within the GitHub trust domain, not an independent publisher signature.
Downloaded .NET SDK archives are separately checked against Microsoft’s published SHA-512 before extraction. Exact-version staged-host verification remains a separate correctness check before promotion.
v0.1.0 remains available as legacy history and predates the checksum-verifying stable-release policy.