Shipped · Observability

What prometheus-operator/prometheus-operator shipped

The public repository of Prometheus-operator · github.com/prometheus-operator/prometheus-operator

Written by FoxPlug from public releases; not affiliated with Prometheus-operator. An automatic summary of the public release, pull request and commit data of github.com/prometheus-operator/prometheus-operator. Prometheus-operator did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

Follow prometheus-operator's weekly shipped digest

Week of September 21, 2026

What shipped

Why it matters

Version 0.94.1 fixes critical RBAC issues that affected finalizer operations and makes permissions more restrictive. Several validation improvements for remote write and receiver configurations enhance reliability and security of alerting configurations.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Prometheus-operator 0.94.1 is out. This release fixes RBAC permissions for finalizers and continues improving validation for alerting receivers and remote write configurations.

Post for LinkedIn

Prometheus-operator 0.94.1 is now available. This release addresses RBAC permission scoping for the operator service account, fixes ThanosRuler remote-write field filtering, and adds URL validation for alerting receivers. Updates include improved status handling for AlertmanagerConfigs and enhanced permission controls based on repair policies.

Week of September 14, 2026

What shipped

Why it matters

The week focused on improving code quality and testing coverage. Topology sharding now provides better visibility into configuration issues, while new linting checks and vulnerability scanning help catch problems earlier in development.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: topology sharding reports unbalanced configurations, govulncheck workflow added for vulnerability detection, unused and whitespace linters enabled, TLS connection tests for Alertmanager, and documentation grammar fixes.

Post for LinkedIn

This week in prometheus-operator: Topology sharding now reports unbalanced configurations in the Reconciled condition when shard counts don't align with zone counts. We added govulncheck workflow for vulnerability detection and enabled additional linters for code quality. TLS connection verification tests for Alertmanager were introduced, and documentation improvements continue.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-09-29.

Is this your repo? Ask us to remove this page.