Compatibility Matrix Update 2026-06-20

[github-actions]

Automated Pull Request to update compatibility matrix

[soffi-ai]

Soffi AI Summary

This is an automated compatibility matrix update (dated 2026-06-20) that bumps the latest tracked versions of two addons — kube-prometheus-stack and Argo CD — along with their associated images, chart versions, and release summaries.

• kube-prometheus-stack is updated from 86.2.3 → 86.3.2 (chart version 86.3.2). The image kube-webhook-certgen is bumped from 1.8.3 to 1.8.4. The release notes for 86.3.0–86.3.2 were not available, so the summary reflects routine (non-major) dependency updates only.

• Argo CD is updated from 3.4.3 → 3.4.4 (chart version 9.5.21 → 9.5.22). The ArgoCD image is bumped to v3.4.4. The summary is enriched to include documented features from the 3.4.x line (Kubernetes version label alignment with vMajor.Minor.Patch format, ApplicationSet/UI improvements) while retaining the breaking change note about ApplicationSet Cluster Generator label format changes.

Commits

Commit	Summary
afdedbd	Bumps the latest tracked versions in the compatibility matrix: kube-prometheus-stack from 86.2.3 to 86.3.2 (with kube-webhook-certgen image updated to 1.8.4) and Argo CD from 3.4.3 to 3.4.4 (chart version 9.5.21 → 9.5.22, ArgoCD image updated to v3.4.4). Also updates the release summaries for both addons with more detailed feature and breaking change descriptions.

Deploy in Soffi

---

Updated: 2026-06-20 02:01 UTC

[greptile-apps]

Greptile Summary

Automated compatibility matrix update for June 20, 2026, bumping two components to their latest versions.

• Argo CD: version advanced from 3.4.3 → 3.4.4 (Helm chart 9.5.21 → 9.5.22, image quay.io/argoproj/argocd:v3.4.4); the ApplicationSet Cluster Generator label-format breaking change (originally from 3.4.1) is now properly split across features and breaking_changes in the summary.
• kube-prometheus-stack: version advanced from 86.2.3 → 86.3.2 (image kube-webhook-certgen bumped 1.8.3 → 1.8.4); the generated summary explicitly admits that release notes for intermediate patch versions 86.3.0–86.3.2 were unavailable, resulting in prose disclaimer strings populating features and breaking_changes list fields instead of empty lists.

Confidence Score: 4/5

Safe to merge; changes are pure data updates to YAML compatibility files with no runtime logic affected.

Both component upgrades are straightforward version bumps. The Argo CD entry is clean. The kube-prometheus-stack entry's generated summary openly acknowledges that release notes for 86.3.0–86.3.2 were not available at generation time, so any breaking changes in those patch releases are undocumented in this matrix. The features and breaking_changes fields also contain prose disclaimer strings rather than empty lists, which may surface unexpectedly if consumers iterate over these fields.

static/compatibilities/kube-prometheus-stack.yaml — incomplete release note coverage for 86.3.0–86.3.2 and prose disclaimer values in structured list fields.

Important Files Changed

Filename	Overview
static/compatibilities/argo-cd.yaml	Bumps Argo CD from 3.4.3 to 3.4.4, updates chart from 9.5.21 to 9.5.22 and image to v3.4.4; refactors summary to split the ApplicationSet label-format breaking change into separate features/breaking_changes entries
static/compatibilities/kube-prometheus-stack.yaml	Bumps kube-prometheus-stack from 86.2.3 to 86.3.2 and kube-webhook-certgen from 1.8.3 to 1.8.4; summary text explicitly acknowledges missing release notes for 86.3.0–86.3.2, and list field values read as prose disclaimers rather than structured data
static/compatibilities.yaml	Mirrors both component-file changes in the aggregate compatibility listing; no additional logic, just duplicate of the per-file updates

_{Reviews (1): Last reviewed commit: "Updated compatibility matrix 2026-06-20" | Re-trigger Greptile}

[greptile-apps]

Prose disclaimers as structured list values

The features and breaking_changes fields are YAML sequences, but their only items are human-readable disclaimers ("No new features are described in the provided notes..." / "None mentioned in the provided notes."). If downstream consumers iterate over these lists expecting real feature strings or breaking-change descriptions, they will surface these disclaimer sentences verbatim to end users. Prefer empty lists ([]) to signal "no data" rather than a single prose disclaimer item, which is consistent with how other entries in the file represent absent data.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

chart_updates acknowledges incomplete release note coverage

The chart_updates value explicitly states that release notes for versions 86.3.0–86.3.2 were unavailable when this entry was generated. This means any breaking changes or notable updates introduced in those three patch releases are not captured here. If a breaking change lands in 86.3.x, users upgrading past 86.2.3 will receive no warning from this matrix entry. It's worth re-running the data collection once upstream release notes become available and updating accordingly.