Conversation
The committed .github/dependabot.yml still pointed at the pre-migration layout (pip /api, pip /, docker /api, gomod /cli) — it scanned the now-archived Python backend (generating dead PRs against deleted uv.lock / pyproject.toml) and did not cover the actual Go server or dashboard at all. The /server and /server/dashboard Dependabot PRs were only appearing via repo-wide *security* updates, which ignore this config. - dependabot.yml: rewrite for the real structure — gomod /server, gomod /cli, npm /server/dashboard, docker /server (Dockerfile + Dockerfile.cuda), github-actions /. Python (legacy/python-api) is intentionally NOT scanned (archived, not built/deployed). Light grouping per ecosystem to cut PR noise. - go-git/go-git/v5 5.19.0 → 5.19.1 (folds in #55 — clean patch, used by the repo-clone path). - react-router 6.30.3 → 6.30.4 lockfile-only (folds in the safe half of #69; within the existing ^6.28.0 range). Deliberately NOT included: vite 5.4.21 → 8.0.16 (#69/#70) — a 3-major jump driven by an esbuild advisory that only affects the dev server (never run in prod; the dashboard is built to static assets and embedded). Needs a dedicated upgrade PR, not a rubber-stamp. Tested: `go build ./...` + `go test ./...` (server, all green); `npm run build` (dashboard builds clean on vite 5 with react-router 6.30.4); dependabot.yml validated as YAML. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…bumps chore(deps): fix stale Dependabot config + fold in safe dep bumps (go-git, react-router)
Upstream ghcr.io/ggml-org/llama.cpp:server-cuda moved past the pinned digest. Bump 67bf4625 → 2ea4be99 (current latest, verified via imagetools inspect). The digest is pinned because the image layout has shifted before (the libllama-server-impl.so split that took prod down with exit 127) — so this must be validated with a scout-cuda rebuild + a GPU smoke test that llama-server resolves all libs and embeddings actually run on the GPU before it goes anywhere near a release. Addresses the weekly llama.cpp-pin-freshness issues #84 #83 #82 #58. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
chore(server/cuda): bump pinned llama.cpp digest to 2ea4be99
Three UI fixes reported from the Home page: - Version rendered "vv0.11.0…": the server version string already carries its leading "v" when built from a release tag (server/vX.Y.Z), but the UI also hard-prefixed "v". Add lib/version.ts → formatVersion() which normalizes to exactly one leading "v" (robust for both tagged builds and the "0.0.0-dev" placeholder), and route all four display sites through it: Footer (now "cix (v0.11.0)" — version parenthesized), HomePage status stat, and the UpdateBanner's available/running lines. - HomePage status panel: rename the "Sidecar" stat to "Provider" — the embedding provider isn't necessarily an in-process sidecar (can be a remote ollama/voyage/openai backend), so "Provider" is accurate either way. - HomePage CLI blurb claimed `cix --help` "does everything the dashboard does, plus reindex…". Untrue — the CLI does code search/navigation + local indexing but not server administration (users, API keys, runtime config). Reword to state that split accurately. Source-only; dist is rebuilt at image build. Dashboard builds clean (tsc + vite). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
fix(dashboard): cosmetic — version double-v, provider label, CLI blurb
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.
Release PR rolling
develop→main. Patch release on top ofserver/v0.11.0— chores/fixes/cosmetics only, no schema or API changes.Highlights
Sidecar
server-cudadigest67bf4625…→2ea4be99…(chore(server/cuda): bump pinned llama.cpp digest to 2ea4be99 #89). Validated end-to-end on the RTX 3090: built + scanned (0 HIGH/CRITICAL),/app/llama-serverresolves all libs (the historic exit-127 layout break did not recur), embedding model resident in GPU VRAM.Dependency hygiene
.github/dependabot.yml(chore(deps): fix stale Dependabot config + fold in safe dep bumps (go-git, react-router) #88): it still described the pre-migration layout (pip/api, root pyproject, gomod/clionly). Rewritten for the real structure — gomod/server+/cli, npm/server/dashboard, docker/server, github-actions. Archivedlegacy/python-apino longer scanned (was generating dead PRs).Dashboard cosmetics (#90)
vv0.11.0…— newformatVersion()normalizes to a single leadingvacross Footer (cix (v0.11.0)), Home status stat, and the update banner.Sidecarstat →Provider(the embedding provider may be remote, not an in-process sidecar).Commits since
server/v0.11.02ea4be99Release steps (T9, after merge)
cd server && make scout-cuda→ verify 0 HIGH/CRITICAL (already clean for this digest)git tag server/v0.11.1 && git push origin server/v0.11.1release-server.ymlbuilds + pushes:v0.11.1,:latest,:v0.11.1-cu128,:cu128:v0.11.1-cu128Issues
Closes #84, #83, #82, #58 (weekly llama.cpp pin-freshness — satisfied by #89).
🤖 Generated with Claude Code