Release v0.8.17 - #181
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Version bump only — 0.8.16 → 0.8.17 across the five manifests.
Three merged changes:
durable_sessions(last_seen_at_ms DESC, session_key).stream_sessionssorted the snapshot walk with no supporting index, so SQLite built a spilling temp B-tree. Measured on a 2,500-session / 1.13 GB corpus: peak +286.7 MB → +0 MB,stream_sessions8.568 s → 3.792 s. Ledger schema v8 → v9; the one-time index build measured 3.74 ms on a 4,826-row corpus, sincedurable_sessionsis narrow and the multi-GB blobs live in a separate table.gpt-daybreak-blue-latestmaps togpt-5.6-sol, clearing a fallback-rate warning on usage that was already priced correctly. Rate card v9.Not exercised in any recording yet: the post-VACUUM WAL checkpoint shipped in v0.8.16, and now this index migration on a real multi-GB ledger.
🤖 Generated with Claude Code