From 84551616c3b2e6279e1173b2c718bbd787f1dd88 Mon Sep 17 00:00:00 2001 From: Jonathan Bell Date: Wed, 16 Sep 2026 12:28:21 +0000 Subject: [PATCH] chore(chart): bump to 0.3.26 for the run-budget and refill env #982 added two env vars to the edge-functions workload (GITHUB_ASYNC_WORKER_ORG_SLOT_CONTINUOUS_REFILL and the conditionally rendered ..._RUN_BUDGET_SECONDS), two values keys, and three new rules in validations.yaml -- but left Chart.yaml at 0.3.25, which is the version currently deployed to production (helm revision 87, 2026-09-14 02:00:58). prod-charts' build-images.yml packages and pushes the chart from Chart.yaml verbatim with no guard against an existing tag, so building main as-is would republish 0.3.25 in Harbor with different contents. That makes the deployed release's recorded chart version stop identifying what is actually running, and makes "roll back to 0.3.25" ambiguous. No template changes here -- only the version. Co-Authored-By: Claude Opus 5 (1M context) --- charts/pawtograder/Chart.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charts/pawtograder/Chart.yaml b/charts/pawtograder/Chart.yaml index 9d61bdc37..2e31e4f10 100644 --- a/charts/pawtograder/Chart.yaml +++ b/charts/pawtograder/Chart.yaml @@ -7,7 +7,7 @@ description: | Studio, postgres-meta, supavisor) so the whole stack can be deployed to a Kubernetes cluster from a single Helm release. type: application -version: 0.3.25 +version: 0.3.26 appVersion: "0.0.1" kubeVersion: ">=1.27.0-0" home: https://pawtograder.net