feat: allow per-project base image pinning via OPENCLAW_BASE_TAG#1
Merged
Conversation
Same override mechanism as openclaw-lagoon PR #30: a project or environment-level Lagoon variable (build scope) OPENCLAW_BASE_TAG overrides the default image tag. Needed here so migrating instances can be pinned to their current version for deterministic rollback. Release and validate workflows updated for the new format.
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
1 participant
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.
Same override mechanism as amazeeio/openclaw-lagoon#30 (verified there on a live Lagoon environment — see that PR for test details): a build-scope Lagoon variable
OPENCLAW_BASE_TAGat project or environment level pins the base image version; without it, behaviour is unchanged (defaultv2026.7.2-beta.2_7).Why this frozen repo needs it: during the node→basic-single migration (openclaw-lagoon#27), a migrating instance gets pinned to its current version so the storage move is separated from the version upgrade — and rollback to this repo redeploys the exact version the instance ran before, instead of forcing the (NFS-broken) upgrade to the frozen default tag.