Release Notes v2.22.0 August 2026

Notable Changes

CLI update to v1.9.76Terraform provider update to v0.3.2

‍Core Features

UI / Notifications / Pull Request Badges

Fianu posts a compliance badge comment on pull requests, and you choose which controls it covers. Set coverage once for the organization, then opt controls in individually and narrow them to the base branches that matter.

How to Use

1. Navigate to Settings > Notifications and enable Pull request badge
2. Set Control coverage to All controls, or to Selected controls to opt in one at a time
3. For Selected controls, open Console > Controls, select a control, choose Edit, and enable the badge in its Notifications section — scope it to a base branch pattern from the same row

UI / Console / Rego Editor

The rule editor formats Rego as you paste and as you run, so a rule pasted from anywhere lands readable. Violations open in their own panel, and official controls state up front which parts of them you can edit.

How to Use

1. Navigate to Console > Controls, select a control, choose Edit, and author the rule in the Rule section
2. Or open the developer console at /console/playground
3. Select Violations to inspect the results of a run

UI / Environments / Environments and Targets

Environments describe the context a deployment runs in and the events that match it. Targets describe where the deployment lands — an EKS cluster, a Cloud Run service, an AKS namespace — and both deploy and read like every other standard entity.

How to Use

1. Navigate to any repository or application
2. Select the "Deployments" icon

API / Teams / Identity Provider Managed Teams

Bind an Auth0 Organization group to a Fianu team and its membership follows your identity provider. Fianu reconciles on a webhook the moment the group changes, and on a recurring sweep regardless, so a dropped event is survivable rather than permanent. While a team is bound, manual membership writes are refused — the group is authoritative.

How to Use

1. List the groups available to your organization with GET /team/groups
2. Bind one to a team with PUT /assets/teams/{team_uuid}/idp-group or select it through the UI
3. Remove the binding with DELETE to return the team to manual membership

Platform / Signing / Sigstore v2 Verification

Image signatures produced by cosign v3 now verify natively. Those signatures are published as OCI 1.1 referrers rather than a .sig tag, so they verify with sigstore-go against the trusted root, while earlier bundles continue through cosign unchanged.

Benefits include:

• No re-signing required for images already in your registry
• Trust roots distributed over TUF, updated without a client change

‍Other Improvements

• Findings render markdown in the violations sidebar
• Command-click opens an entity in a new tab
• Gates are selectable in the ticket entity-type filter
• General UI/UX improvements
• Bug fixes

‍