Fix bug reports, bump deps - #310
Merged
Merged
Conversation
4 tasks
bussyjd
added a commit
that referenced
this pull request
Apr 7, 2026
… Trivy precision Address review findings from #310 merge: - fixVolumeOwnership: thread *ui.UI through the full call chain (ensureWallet → GenerateWallet → provisionKeystoreToVolume → fixVolumeOwnership) so chown failures surface via u.Warnf, uniform with the rest of the codebase (zero log.Printf in openclaw package) - fixVolumeOwnership: reject paths outside DataDir (../ traversal guard) to prevent docker exec targeting unexpected node paths - docker-publish-x402: remove broken matrix outputs (both pointed to last-finishing job), scan by SHA tag instead of :latest for deterministic Trivy results matching the exact build - obolup.sh: warn before restarting Ollama service, only restart if already active to avoid disrupting running inference
OisinKyne
pushed a commit
that referenced
this pull request
Apr 7, 2026
…ion (#311) * fix: harden PR #310 — thread ui.UI for chown errors, path validation, Trivy precision Address review findings from #310 merge: - fixVolumeOwnership: thread *ui.UI through the full call chain (ensureWallet → GenerateWallet → provisionKeystoreToVolume → fixVolumeOwnership) so chown failures surface via u.Warnf, uniform with the rest of the codebase (zero log.Printf in openclaw package) - fixVolumeOwnership: reject paths outside DataDir (../ traversal guard) to prevent docker exec targeting unexpected node paths - docker-publish-x402: remove broken matrix outputs (both pointed to last-finishing job), scan by SHA tag instead of :latest for deterministic Trivy results matching the exact build - obolup.sh: warn before restarting Ollama service, only restart if already active to avoid disrupting running inference * refactor: migrate fmt.Print* output to ui.UI in CLI commands Route all CLI output through the ui.UI layer instead of raw fmt calls. This ensures all output respects --verbose, --quiet, and future --output json mode (Phase 1C of cli-agent-readiness plan). - sell.go: 77 fmt.Print* calls → u.Infof/Warnf/Successf/Printf - network.go: 28 fmt.Print* calls → u.Infof/Warnf/Successf/Printf - model.go: 17 fmt.Print* calls → u.Infof/Warnf/Successf/Printf Thread u *ui.UI into standalone helpers that previously used fmt directly: removePricingRoute, runInferenceGateway, registerSponsored, registerDirectViaSigner, registerDirectWithKey. --------- Co-authored-by: bussyjd <bussyjd@users.noreply.github.com>
4 tasks
bussyjd
added a commit
that referenced
this pull request
May 15, 2026
…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
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.
No description provided.