Skip to content

Releases

For the currently approved stable release, consult the technical release notes and installation guide. GitHub also lists the latest published release, which is a publication pointer rather than independent evidence of qualification. The installation guide lists qualified platforms, version-specific archive names and checksum steps.

This page keeps a historical snapshot below; its version-specific statements are not a claim about later releases.

Download and install

Use the shell installer, Homebrew or the latest published public release archives. Follow Install Runtime for the approved version, supported platforms and checksum verification.

The executable is engrt on macOS/Linux or engrt.exe on Windows. The shell installer and Homebrew support macOS/Linux; Windows uses verified ZIP/manual installation.

Before upgrading automation, read Upgrading. For the historical v0.13.0 release, config v2, policy v3 and version: v1 capabilities were retained. Later releases may differ.

v0.13.0 release highlight — October 21, 2026

What changed

  • Destructive effects are refused on every route. Repository deletion, remote ref deletion, forced pushes and other history rewriting, and removal of branch protection and rulesets are refused by the compiled safety profile on REST, GraphQL, native CLI and capability paths, even under a policy that explicitly allows them. Nothing is sent.
  • Refusals say why, truthfully. Each refusal names its class (policy, compiled_safety, context_unsupported, argument_invalid, auth), its rule, a reason and a recovery hint, in the terminal and in --output json. "Policy denied" is said only of a policy refusal, and audit records of refusals show that nothing was dispatched.
  • Nested request bodies. key:=<json> carries an object, array or other JSON value into a REST body or GraphQL variable, for example a repository ruleset.
  • Safer GitHub arguments and guidance. An owner, repository or organization that is not a single path segment is refused before authentication. Hosts without an OS secure store are told which store-free sources work.
  • CLI polish. engrt command run --help and engrt resolve --help print help, and id-token: write is visible in dry-run diffs while real secrets stay redacted.

Before upgrading automation, check the compatibility changes: the newly refused forms, the changed denial wording, command run <binary> -- … now refused, repeated fields now refused, and callers that declare nothing now recorded as undeclared.

Known limitations: the destructive catalog is finite and lexical, not a sandbox, and Git aliases or push settings in repository or user config files are not visible to it. Live GKE was not qualified, and release archives do not yet bundle third-party licence notices. See the technical release notes for the complete contract and limitations.

Earlier releases

The technical release notes retain earlier release details and compatibility requirements.

Design Principle

Verify the release version and checksum before installation.