chore: bump frontend to v2.37.3, backend to v2.44.0 and Plumber chart to 1.5.3 - #62
Merged
Merged
Conversation
Updates the frontend image tag to v2.37.3 in versions.env and values.yaml. The Plumber chart version is also incremented to 1.5.3 to reflect these changes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The frontend and chart moved in this PR but the backend stayed on v2.43.2, which would ship 1.5.3 with a backend two releases behind the images that are actually published. v2.44.0 is the current backend build on Docker Hub. Updated in the three places a tag lives: versions.env for compose, and both values.yaml entries, since the backend image also backs the worker deployment. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WkEoFQP5bxWXS5qgkYxmu8
thomasboni
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the deployment to the current published images and bumps the chart to match.
The backend tag lives in three places and all three moved:
versions.envfor compose, and bothvalues.yamlentries, since the backend image also backs the worker deployment.Both tags are the newest builds on Docker Hub (
getplumber/frontend:v2.37.3pushed 2026-09-09,getplumber/backend:v2.44.0pushed 2026-09-08).helm lintpasses and the rendered manifests reference exactly those two images; theJOBS_WORKER_TASK_MAX_RUNTIMEwatchdog still renders on the worker only.🤖 Generated with Claude Code
https://claude.ai/code/session_01WkEoFQP5bxWXS5qgkYxmu8