Repository navigation
v0.2.0
What's Changed
This release introduces optional disposable Linux container execution for csrun, so manifests can run the same engine inside a container with the selected .NET SDKs preinstalled, backed by a release pipeline that verifies and publishes those images.
- Container execution runs manifests piped from stdin in an unprivileged Linux container, with the image pinned to the latest released engine asset and verified by checksum, while generated code and build artifacts stay in container-owned storage,
- Host isolation passes no host mounts, credentials, or Docker socket by default, so the container does not reach into the host unless you opt in,
- SDK environment images are built from exact SDK inputs with deterministic tags, and duplicate or unsupported channels are rejected before any publishing happens,
- OCI verification and promotion tooling checks image archives before they are promoted, and verified images are attached to draft releases,
- CI and release validation runs container tests in pull request and release workflows, adds a required quality gate to the PR workflow, and pins runners to
windows-2025andubuntu-26.04, - Docker Hub deployment adds a production workflow for publishing the verified images,
- Documentation covers container usage, SDK environment publishing, validation results and their limits, and the fixed Ubuntu runner policy.
Sources:
- V0.2.0/container isolation by @gimlichael and @aicia-bot in #3
Full Changelog: v0.1.0...v0.2.0