chore(frontend): bump obol-stack-front-end v0.1.23 → v0.1.24 (digest-pinned)#482
Open
bussyjd wants to merge 1 commit into
Open
chore(frontend): bump obol-stack-front-end v0.1.23 → v0.1.24 (digest-pinned)#482bussyjd wants to merge 1 commit into
bussyjd wants to merge 1 commit into
Conversation
4 tasks
00b85b6 to
16a6b3e
Compare
…pinned) Bumps the frontend image to the new stable v0.1.24 release and switches the pin format from tag-only to tag+digest. Image: obolnetwork/obol-stack-front-end:v0.1.24@sha256:d5abd6aebddcabf7b7fccd2f5e922cb6067c90dca808b306bd46db71b0010206 What v0.1.24 contains (cumulative since v0.1.23): - 12 Dependabot dep bumps via frontend #310: - Runtime: next 16.2.6, react 19.2.6, @rainbow-me/rainbowkit 2.2.11, @copilotkit/{react-core,react-ui} 1.57.1 - Dev: @typescript-eslint/{parser 8.59.2,eslint-plugin 8.59.1}, @next/eslint-plugin-next 16.2.6, eslint-config-next 16.2.6, @types/node 25.6.2 - Infra: Dockerfile node:22-alpine → node:26-alpine, actions/setup-node 6.3.0 → 6.4.0 - feat(dashboard): storefront link + AgentRegistrationCard (frontend #292) Supply-chain review on the frontend dep diff: GREEN - Zero net-new transitive packages (4 chevrotain sub-deps consolidated) - All workflow uses: SHA-pinned (setup-node SHA verified against v6.4.0 tag) - All target versions ≥4 days old on npm - No new install scripts - Peer-dep compatibility verified - node:26-alpine multi-arch index verified on Docker Hub - PR #292 new API route consumes operator-controlled tunnelURL from in-cluster ConfigMap (no SSRF/user-input surface); no dangerouslySetInnerHTML; consistent with existing /api/agents/* auth patterns
16a6b3e to
6e1a93f
Compare
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
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 frontend image pin from
v0.1.23(tag-only) to stablev0.1.24with multi-arch digest:Single commit; combines the version bump with the supply-chain hardening that was previously staged in #468 (digest-pin at v0.1.23). #468 closed as superseded.
What v0.1.24 contains (frontend-side)
Cumulative since
v0.1.23:next16.2.4→16.2.6,react19.2.5→19.2.6,@rainbow-me/rainbowkit2.2.10→2.2.11,@copilotkit/{react-core,react-ui}1.56.3→1.57.1@typescript-eslint/{parser 8.59.2,eslint-plugin 8.59.1},@next/eslint-plugin-next 16.2.6,eslint-config-next 16.2.6,@types/node 25.6.2node:22-alpine→node:26-alpine;actions/setup-node6.3.0 → 6.4.0feat(dashboard): storefront link + AgentRegistrationCardFrontend release sequence:
v0.1.24-rc1(dep bumps only) →v0.1.24-rc2(+ #292) →v0.1.24(stable, same code as rc2, freshly-built Docker image).Supply-chain review (frontend-side): GREEN
Audited via security subagent on both #310 (dep diff) and #292 (feature diff):
uses:SHA-pinned (verifiedactions/setup-node@v6.4.0SHA matches the public tag)node:26-alpinemulti-arch OCI index verified on Docker Hub/api/agents/registrationroute consumes operator-controlledtunnelURLfrom in-clusterobol-stack-configConfigMap (no SSRF/user-input surface); nodangerouslySetInnerHTML; consistent with existing/api/agents/*auth patternsMulti-arch digest
sha256:d5abd6…010206is the OCI image index coveringlinux/amd64+linux/arm64. Note: this is a different digest thanv0.1.24-rc2(sha256:cdcc8c…2ba4c) because the Docker images were rebuilt for thev0.1.24tag — same git SHA, different binary digests (typical for non-reproducible Docker builds).Why digest-pin
Mutable tag pins allow a registry-credential compromise to silently swap image contents under the same
v0.1.24tag on the next pull. Thename:tag@digestformat renders to a valid OCI reference via theobol-appchart'sobol-app.imagehelper; the digest is authoritative at pull time, the tag stays for human readability.Test plan
lint-testCI greenobol stack uppulls the new digest and frontend pod becomes Readyobol-stackRC at maintainer discretionNot self-merging
Per
feedback_main_merge_gates.md: requires flows-green (flow-11 + flow-14 receipts) AND a second human reviewer. Maintainer hand-off.