Release Notes v0.93
Release v0.93 brings no-code release approval gates, operational actions generated with your modules, a Git-backed module registry with generated CI, and a shared GitHub App installation with permission health surfaced in Facets.
✨ What's New
No-Code Release Approval
Projects now have a dedicated Release Approval settings page for gating releases behind a manual decision, with no scripting required. Pick the environments, resources or release streams that should be gated and choose how they combine, and any matching release stops at Pending Approval until an authorized approver acts on it.
A release parked at a gate holds that environment's release queue until it clears, and Facets captures the Terraform plan the moment a release is gated, so the approver can review exactly what will change before deciding.
Operational Actions on Modules
Modules can now ship operational actions: buttons that act on infrastructure you have already deployed, such as scaling a deployment, restarting pods, snapshotting a database or pulling a kubeconfig. Praxis offers them at the end of every module build and writes them into the module as Terraform.
Because they deploy with the module, an action appears on every instance of that resource in every environment where the module is deployed, with no per-environment setup.
Git-Backed Module Registry
The module registry can now be backed by a Git repository, connected from the Module Registry page by either migrating your existing modules into a new repo or attaching one you already have. Migration bootstraps the repository and commits a generated CI workflow that publishes modules into the registry on merge, so module changes follow the same review path as the rest of your code.
Shared GitHub App Installation
A single GitHub App installation on your organization now serves Facets and Praxis together, rather than each holding its own credentials. For an organization-level installation Facets no longer stores a long-lived token at all, minting a short-lived installation access token on demand instead.
Permission health is now visible where you manage accounts. When an installation needs permissions a GitHub organization admin has not yet approved, the Accounts page shows a Permissions update pending state along with which permissions are missing and why, plus a copyable approval link you can hand to an admin.