Release notes: September 3, 2025

Maturity & reporting

• Turn off maturity for certain component types: Keeps your maturity views focused on what you actually govern (e.g., services) and omits components that shouldn’t affect levels or roll-ups. That means cleaner dashboards and more credible scorekeeping. See how component maturity is reported and rolled up in the Component Maturity Report and the per-component Maturity Report.
• Filter maturity reports by Component Type: Quickly answer questions like “How are just our services doing vs. our infrastructure components?” so teams can prioritize improvements where they matter most. This builds on the same maturity reporting surfaces already in the product.

• Filter components by “maturity enabled”: Separate what’s in scope for maturity from what isn’t — handy for audits, campaigns, and owner follow-ups. Pairs naturally with component type management and the maturity views in OpsLevel.

Read the docs → 

Checks & quality gates

• Code Issues checks: fail by default when no project is attached. “No data” is often a risk — failing by default prevents blind spots and prompts owners to link the correct project so issues can be evaluated. This ties directly to how Code Issues projects map to components.
• New Relationship Check (in app & Terraform): Enforce catalog integrity automatically. Verify that required relationships exist (and even their counts), so your reports and dependency views stay accurate without manual policing. You can manage these checks in the app or as code via the Terraform provider. 

MCP, integrations & automation

• Improved reporting from MCP: MCP exposes your catalog, checks, and more to AI tools. Better reporting means clearer insights when you use AI to query architecture, standards, or ownership, leading to faster decisions grounded in real catalog data. Read the docs → 

• Custom Integration Extract/Transform editor upgrades (syntax highlighting, folding, line numbers, mono font): Building and maintaining data mappings is easier and less error-prone. Clearer transforms mean cleaner custom properties and more trustworthy reports. See Custom Integrations and mapping guides. Read the docs →
• Updated Syft (SBOM) support, including UV: Broader SBOM compatibility → more complete package inventories → stronger package/version checks. This helps teams spot vulnerable or out-of-support packages across repos and services. See Package Version Inventories. Read the docs →
• Kubernetes agent: auto-create and map components to services: Less manual curation, more up-to-date catalog. Automating discovery/mapping from K8s keeps service records fresh and cuts onboarding toil. Learn more in the OpsLevel Agent and Kubernetes Integration docs. Read the docs →
  
  

Bug fixes

• Fixed bug where actions weren't being triggered when using the API

‍

Stay on top of release notes and other updates from OpsLevel by subscribing to our newsletter.

‍

‍

‍
‍

‍
‍