Conversation
The images are on Docker Hub — dvcdsys/code-index:v0.14.0 and :latest at 14:31 UTC, :v0.14.0-cu128 and :cu128 at 14:20 — so the site may now say so. Order matters and this is the second half of it: the site advertises only an already-published release, which is why the version bump is a separate change after the tag rather than part of it. release-server.yml's "Check the site advertises this release" job is deliberately non-blocking for the same reason; it annotated this release asking for exactly this bump. CLI_VERSION is untouched at 0.10.2 — the CLI is on its own tag stream and has not been released alongside this. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
chore(site): advertise server 0.14.0
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.
One-line follow-up to the
server/v0.14.0release. The site auto-deploys frommain, so the version bump only takes effect once it lands here.The whole diff:
site/src/shared/versions.js,SERVER_VERSION'0.13.0'→'0.14.0'.Why it is a separate PR rather than part of the release
The site may only advertise an already-published release. So the order is: tag → images land → bump.
release-server.yml's Check the site advertises this release job is non-blocking for exactly this reason, and it annotated the release asking for this bump.The images it now points at are live:
dvcdsys/code-index:v0.14.0dvcdsys/code-index:latestdvcdsys/code-index:v0.14.0-cu128dvcdsys/code-index:cu128CLI_VERSIONuntouched at0.10.2— separate tag stream, not released alongside this.Still open after this, and neither is a site concern
:v0.14.0-cu128is published unscanned because the GPU host is unreachable. Run the gate against the published tag, and bumpcloudflared(2026.7.3→2026.8.2), before any prod deploy.llama.cpp:server-cudadigest exists (fd68d130…→995fe9f2…). Bumping it needsmake scout-cudato validate the shared-library layout — also blocked on the GPU host.