Isolated .NET SDK Exact SDKs without changing system .NET

Isolated .NET SDK v0.3.0

Released October 5, 2026.

v0.3.0 improves the stable installation path, makes the tool’s own release identity explicit, adds lifecycle-aware SDK auditing, expands interactive verification, and strengthens release verification and documentation.

Highlights

  • Verified latest-stable bootstrap — the short Pages-hosted PowerShell and Bash commands resolve the latest stable release, verify the selected tagged product script against that release’s SHA256SUMS, and execute only the verified tagged bytes.
  • Explicit tool identity — stable copies report their exact release tag through -Version / --version, while mutable main remains clearly identified as development source. Main displays the same identity.
  • SDK lifecycle Audit — Audit compares both Isolated SDKs and read-only System SDKs with current Microsoft release metadata and reports servicing and lifecycle state without modifying either inventory.
  • Interactive Verify — the read-only exact-version isolated-SDK health check is available from persistent interactive sessions as well as direct commands.
  • Stronger release verification — stable publication stamps the requested tag into both product scripts in a derived release commit and supports independently rerunnable verification of the public release, checksum asset, bootstrap paths, saved bytes, and embedded identity.
  • Improved documentation — task-focused documentation and site navigation cover commands, concepts, contracts, release behavior, and maintainer procedures more directly.
  • Bootstrap and portability fixes — release-index parsing no longer emits the GNU awk warning, transient curl receive failures are retried in latest-stable E2E/bootstrap paths, and HTTP failures retain terminal failure semantics.

Release and trust model

v0.3.0 is the first stable release published with embedded tool-version identity. The publication workflow derives the release commit from the already-validated main commit and changes only the two product-script identity markers before calculating release checksums.

Latest-stable and pinned bootstrap both verify the tagged product script against the selected release’s SHA256SUMS before the product script executes. The checksum and tagged source share the project’s GitHub trust domain; this provides integrity checking, not an independent publisher signature.

v0.2.0 remains historical release state and is not rewritten to retrofit embedded identity.

More details