chore: bump frontend image to v0.1.28-rc0 (draft — digest pending)#677
Draft
bussyjd wants to merge 1 commit into
Draft
chore: bump frontend image to v0.1.28-rc0 (draft — digest pending)#677bussyjd wants to merge 1 commit into
bussyjd wants to merge 1 commit into
Conversation
Bumps the obol-frontend Helm values image tag and the dev-frontend-reset justfile recipe to consume front-end v0.1.28-rc0 (ObolNetwork/obol-stack-front-end#417: bundled dependency bumps + probe-surface removal). DRAFT: the Helm pin is intentionally un-digested. The authoritative multi-arch sha256 digest only exists after the v0.1.28-rc0 image is published (front-end #417 merged + tag pushed + build-push-deploy). Re-pin tag: "v0.1.28-rc0@sha256:<digest>" and mark ready before merge. Claude-Session: https://claude.ai/code/session_01QXX79ZAedwYzBegvhkgjDV
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.
Summary
Bumps the front-end Docker image consumed by obol-stack to v0.1.28-rc0, the RC cut in ObolNetwork/obol-stack-front-end#417 (bundled dependency bumps + removal of the dead x402 probe surface).
Changes:
internal/embed/infrastructure/values/obol-frontend.yaml.gotmpl—image.tagv0.1.26@sha256:7a61…→v0.1.28-rc0(digest TODO)justfiledev-frontend-reset—…front-end:v0.1.25→…front-end:v0.1.28-rc0Why this is a draft
The Helm pin is digest-pinned (
tag: "vX.Y.Z@sha256:…") by the v0.10.0-rc2 supply-chain hardening, so the authoritativesha256can only be computed after the multi-arch image is published. That happens once front-end #417 merges, thev0.1.28-rc0tag is pushed, andbuild-push-deploy.ymlpublisheslinux/amd64 + linux/arm64.Before marking ready: re-pin to
tag: "v0.1.28-rc0@sha256:<multi-arch index digest>"(and optionally add the digest to the justfile recipe to match). Renovate'sobol-stack-front-endimage rule may also raise this automatically once the image is live.Notes
v0.1.27-rc0); base is currentmain(still onv0.1.26). Close/redirect chore: bump frontend image to v0.1.27-rc0 #617 as you prefer.https://claude.ai/code/session_01QXX79ZAedwYzBegvhkgjDV