This generated queue turns upstream Helm chart movement into concrete work.
It separates five cases:
- a retained candidate still matches latest upstream and needs a replacement decision;
- a retained candidate has a written replacement decision and needs only the follow-up named by that decision;
- a retained candidate is proof-complete but already behind a newer upstream chart version and needs refresh work;
- no retained candidate exists yet, so the proof chain must be created first;
- a retained render/package candidate exists and needs root-path promotion plus the remaining ConfigHub and live lanes.
Result
update rows: 7
replacement decisions to write: 0
replacement decisions already written: 7
retained candidates needing refresh: 0
render candidates needing root/live work: 0
new retained candidates needed: 0
p0 rows: 0
p1 rows: 0
p2 rows: 7Queue
| Chart | Current supported | Latest upstream | Retained candidate | Action | Priority | First step |
|---|---|---|---|---|---|---|
argo-cd/argo-cd | 9.5.15 | 9.5.17 | 9.5.17 | replacement-deferred | p2 | keep argo-cd/argo-cd@9.5.15 pinned; revisit argo-cd/argo-cd@9.5.17 after the recorded replacement requirements are satisfied |
bitnami/mongodb | 19.0.7 | 19.1.0 | 19.1.0 | replacement-deferred | p2 | keep bitnami/mongodb@19.0.7 pinned; revisit bitnami/mongodb@19.1.0 after the recorded replacement requirements are satisfied |
bitnami/nginx | 24.0.2 | 25.0.0 | 25.0.0 | replacement-deferred | p2 | keep bitnami/nginx@24.0.2 pinned; revisit bitnami/nginx@25.0.0 after the recorded replacement requirements are satisfied |
bitnami/postgresql | 18.6.7 | 18.7.0 | 18.7.0 | replacement-deferred | p2 | keep bitnami/postgresql@18.6.7 pinned; revisit bitnami/postgresql@18.7.0 after the recorded replacement requirements are satisfied |
bitnami/redis | 25.5.3 | 27.0.0 | 27.0.0 | replacement-deferred | p2 | keep bitnami/redis@25.5.3 pinned; revisit bitnami/redis@27.0.0 after the recorded replacement requirements are satisfied |
prometheus-community/kube-prometheus-stack | 85.3.3 | 86.1.0 | 86.1.0 | replacement-deferred | p2 | keep prometheus-community/kube-prometheus-stack@85.3.3 pinned; revisit prometheus-community/kube-prometheus-stack@86.1.0 after the recorded replacement requirements are satisfied |
prometheus-community/prometheus | 29.8.0 | 29.9.0 | 29.9.0 | replacement-deferred | p2 | keep prometheus-community/prometheus@29.8.0 pinned; revisit prometheus-community/prometheus@29.9.0 after the recorded replacement requirements are satisfied |
Why This Exists
The refresh lane should not collapse into a single vague "upgrade charts" task. Each row has a different safe next action. The queue keeps the supported catalog pinned while making the next proof work visible.
Files
| File | Role |
|---|---|
| queue.csv | Spreadsheet work queue. |
| queue.yaml | Machine-readable work queue. |
| ../replacement-decisions/summary.md | Replacement-decision queue for retained proof-complete candidates. |
| ../../refresh-survival/summary.md | Refresh status across the top-20. |
Verify
npm run top20:latest-action-queue:verify