Repository navigation
chore(site): advertise server 0.15.1 and cli 0.10.3 - #307
Merged
Merged
Conversation
Both tags now exist and both releases have published their artifacts, so the site may claim them. Order matters here and is deliberate: the comment at the top of versions.js and the release flow both require that the site never advertise a version that is not yet tagged, which is why this lands after the release rather than inside it. The release workflow's "Check the site advertises this release" job is non-blocking precisely so the release can go out first and this follow-up can close the gap — so a green release does NOT mean the site is current. It passed on server/v0.15.1 while the site still said 0.15.0. Verified before committing: server/v0.15.1 tag 5182d6b images :v0.15.1 / :latest (digest b1e25f9ea9cce47a) and :v0.15.1-cu128 / :cu128 (digest 343f4bdc2f3b36f5) all published cli/v0.10.3 tag a6ffb88 four platform tarballs + checksums site npm run build OK MAC_APP_VERSION, PLUGIN_VERSION and COWORK_PLUGIN_VERSION are untouched — nothing was cut for them in this cycle. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Closes the gap the release deliberately leaves open: the site may only claim a version that is already tagged, so this lands after the release rather than inside it.
SERVER_VERSION0.15.0 → 0.15.15182d6ba58f4:v0.15.1+:latest(digestb1e25f9ea9cce47a, 77 MB),:v0.15.1-cu128+:cu128(digest343f4bdc2f3b36f5, 1065 MB)CLI_VERSION0.10.2 → 0.10.3a6ffb88c8d6cchecksums.txtBoth floating aliases share a digest with their versioned tag, so
latestandcu128really do point at this release.Worth knowing for next time
release-server.yml's "Check the site advertises this release" job is non-blocking by design, and it passed onserver/v0.15.1while the site still said 0.15.0. A green release therefore does not mean the site is current — this PR is the step that makes it so.Not touched
MAC_APP_VERSION,PLUGIN_VERSIONandCOWORK_PLUGIN_VERSION— nothing was cut for them in this cycle.Verification
npm run buildinsite/passes. Both tags confirmed present on the remote before committing.🤖 Generated with Claude Code