Quirlv0.5.1
Getting started

Status and platforms

The honest support and release-identity boundary for Quirl's 0.4 Unix line.

Release status

Quirl's 0.4 line supports interactive Linux and macOS. A build is an official release only when an immutable GitHub tag and release name its exact commit; untagged source checkouts are candidate or development builds even when their workspace version matches a release. Release gates are tracked in the release checklist, and canonical evidence attribution appears below.

The current supported release is v0.5.1, from commit 3f0064cbd2af644630b7a50e75a57103186b8a91. Install through Homebrew or use the verified native archive for your Linux/macOS target. Check quirl --version before following the 0.5.1 walkthrough. Compatible completion knowledge may advance independently through the version-scoped website asset channel without changing the binary version.

The v0.5.1 native release measurements identify all four published executables, their hosted runner environments, and the passing latency and evidence gates. The 0.1 evidence block below remains historical.

Release evidence status — historical. Artifact evidence for measured candidate 23fd5d36907fc816bdafd9aa3c2dcb3afb69feb5 and artifact 9a893a5f1a0b49d62712f331c88966113d910d94efa9651dc4feffe9fd55b637 is historical. Evidence commit 14e70939d039d96c195f57452a0e1ec3928194af documents that measurement. It is evidence only for that named artifact, not for a later candidate. This historical record does not assert the release-readiness or human-review state of a later candidate.

TargetStatusNotes
LinuxSupported release targetInteractive and non-interactive release target
macOSSupported release targetInteractive and non-interactive release target
WindowsBest effortContract-tested portability; not a supported interactive target
WebAssembly packagesValidation onlyPackages validate, but do not execute

Compatibility boundary

Commands and documentation continue to evolve across releases. Accepted ADRs, frozen protocol descriptors, and the changelog identify the parts that are intentionally stable within a release line.

For the current security-reporting policy, see Security.

On this page