Skip to main content
Sifr stable releases are qualified compiler, sysroot, installer, documentation, and editor artifacts published through one governed release index. The index uses schema_version: 2. It is the authority for active and withdrawn releases.

​
Current stable release

Active stable version: 0.1.0 Withdrawn stable versions: none. These facts are rendered from stable-site-release-facts.json, which is derived from the governed release index during protected publication. A withdrawn version remains in release history but cannot be selected for a fresh install or exact version pin.

​
Install stable

The default and explicit stable entrypoints resolve the same active release:
Pin the current release when you need reproducible setup:
The dispatcher verifies the immutable installer SHA-256 from the governed index. The installer then verifies the target archive and sysroot before replacing an existing toolchain.

​
Update stable

Official standalone installs record their channel in an install receipt.
Use --force only for an intentional same-version reinstall, channel switch, or approved rollback. Stable-looking versions that are absent or withdrawn in the governed index are rejected.

​
Release governance

Stable publication requires a locally passing release profile, an immutable candidate plan, exact artifact digests, and protected approval by a reviewer other than the workflow initiator. During the repository’s temporary single-maintainer period, the schema-v2 bootstrap and first GA may instead use the checked-in, expiring approval waiver. That exception still requires a GitHub-recorded protected approval, binds the waiver digest into retained evidence, and cannot authorize later normal or incident publication. Publication verifies the same candidate bytes before changing the index. rc is not a public channel. If a release is withdrawn, fresh installs and exact pins fail closed. Sifr can roll back only to an active predecessor already named by the approved release plan. The first stable release has no rollback predecessor, so recovery is an incident roll-forward. See compatibility, support, and troubleshooting for operational details.