Releases

AI-analyzed release notes for CNCF graduated and incubating projects.

URGENCY

All Action needed Check if affected Plan ahead

KIND

Category

All AI & ML CI/CD & App Delivery Kubernetes Core Networking & Messaging Observability Orchestration & Management Provisioning & Runtime Security Storage & Data

Project: OpenCostClear ×

OpenCostv1.120.3ObservabilityMay 29, 2026

ACTION 1CHECK 1OTHER 51View full analysis

A maintenance release with dependency updates, correctness fixes, and new cloud and query capabilities. Configuration and output behavior also change, along with a Go dependency upgrade for GHSA-xmrv-pmrh-hhx2 and CVE-2026-34986.

Action needed (1)

securityhighGo dependency upgrades for GHSA-xmrv-pmrh-hhx2 and CVE-2026-34986
Go dependencies are upgraded for GHSA-xmrv-pmrh-hhx2 and CVE-2026-34986.

Check if affected (1)

breakingThe MCP_SERVER_ENABLED default is false
Applies if you do not configure MCP_SERVER_ENABLED.
The MCP server is now opt-in, with MCP_SERVER_ENABLED defaulting to false.

Source ↗

OpenCostv1.120.2ObservabilityMay 18, 2026

ACTION 1CHECK 2OTHER 40View full analysis

A maintenance release with dependency updates, operator-visible configuration and behavior changes, new integrations and capabilities, and correctness fixes. It also includes an explicitly disclosed security-related Go dependency upgrade.

Action needed (1)

securityhighGo dependency upgrades for GHSA-xmrv-pmrh-hhx2 and CVE-2026-34986
Go dependencies were upgraded to address GHSA-xmrv-pmrh-hhx2 and CVE-2026-34986.

Check if affected (2)

breakingThe provider config source, changed
Applies if you configure provider config.
The configuration behavior reads from cloud-integration.json instead of using provider config.
breakingThe MCP_SERVER_ENABLED default, changed to false
Applies if you use the MCP server.
The MCP_SERVER_ENABLED setting now defaults to false, making the MCP server opt-in by default.

Source ↗

OpenCostv1.120.0ObservabilityApr 13, 2026

ACTION 1OTHER 26View full analysis

A maintenance release with dependency updates, defect corrections, expanded compatibility, and new integrations and configuration capabilities. An existing configuration source is replaced, so affected operators need to update their configuration.

Action needed (1)

breakingProvider configuration replaced by cloud-integration.json
The provider config is no longer used, and configuration is read from cloud-integration.json instead. Operators using the replaced configuration source need to update their configuration.

Source ↗

Browse by month