Repository navigation
chore: bump version to 1.18.23-7 - #376
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.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.
Summary
Fork-only revision bump 1.18.23-6 → 1.18.23-7 via
bun bump, following README → Bumping the version. Every workspace manifest moves in lockstep andbun.lockis regenerated by the script. The diff is onlyversionfields. NoDIVERGENCES.mdentry is needed: theversionfield is already documented as deferring to upstream on sync.It carries everything merged since 1.18.23-6:
codev uploadsends them on demand. Session logs upload only viacodev upload --logs(diagnostics moved to--diagnostics). The automatic log uploads and the desktop "Upload Session Logs" menu item are removed.The analysis backend's
upload-session-statsendpoint (oadtq/z8l-ai-hub#9, merged) has to be deployed for these clients' pushes to land. Until then they get a 404, log it quietly and retry at the next launch.After merge, publish with
bun releaseand stage the desktop build withbun run stage-release.🤖 Generated with Claude Code