chore(chart): bump to 0.3.26 for the run-budget and refill env - #992
Conversation
#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) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
🧹 Preview torn down — namespace |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
1 participant
#982 added two env vars to the edge-functions workload
(
GITHUB_ASYNC_WORKER_ORG_SLOT_CONTINUOUS_REFILLand the conditionally rendered..._RUN_BUDGET_SECONDS), two values keys, and three new rules invalidations.yaml— but leftChart.yamlat 0.3.25, which is the versioncurrently deployed to production (helm revision 87, 2026-09-14 02:00:58).
prod-charts'
build-images.ymlpackages and pushes the chart fromChart.yamlverbatim with no guard against an existing tag, so building
mainas-is wouldrepublish 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.
Verified before opening:
helm templateof this chart against the livevalues/values-prod.yamlrenders clean, and the async-worker env comes out asCONTINUOUS_REFILL=1with the run budget absent (so the worker's own deriveddefault of 330s applies at prod's
timeoutMs: 480000).🤖 Generated with Claude Code