Release CodeStory 0.17.7 - #2539
Merged
Merged
Conversation
[codex] 0.17.7: source-bound reads, cross-session preparation, #2531 recoverability, Windows fixes and test-audit remediation
[codex] prepare 0.17.7 versioned calibration source
This branch was successfully deployed
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.
Release CodeStory 0.17.7 with coherent source reads, refresh waiting across sessions, and clearer indexing and recovery diagnostics. The user-facing changes and upgrade behavior are documented under 0.17.7 in the changelog.
PR #2533 was repaired and independently reviewed again until no confirmed flagrant issue remained. The fixes restore immutable permissions on failed publication, share one activation deadline, preserve typed schema refusals and executable recovery guidance, verify retired-directory identity before removal, exclude writer-hold instrumentation from production, and isolate the lexical test counter across threads. The follow-up review found and verified the newer-schema recovery gap before it was fixed. Version preparation is merged through #2535; the independently accepted generated freeze is integrated through #2538.
This PR promotes
dev/codestory-nextintomainwith one tree-preserving merge. The exact frozen candidate is3264c0ec430f9b1ecfe23b1d0266a9312ac0e052, tree5ade9b4cedfa6b8a2e85f650b767b59917acac58. Its sole parent is calibrated source0384641ed81248125737cbf80a31abe63f28a0a0, tree0dd1f99515321091bb5b42c132f2de1c2bf3a6a9; only the generated constant-set file differs. Main currently ends atf3966cadd6d602f2ccb7e4c99e2d8afebe1e19b8.Completed proof:
Albert explicitly requested the 0.17.7 bump and dev-then-main merge in the active task. That instruction authorizes this concrete promotion and its automatic publication. The coordinator records approval against the qualified commit, tree, pre-publication ledger and archive digests before merging. Merging starts the canonical automatic release; publication and post-publication installation/restart closeout remain pending until that workflow proves them. No manual tag or gate bypass is involved.
The core cache moves to schema 36, requiring a one-time rebuild on the next product call. Publication stamps move to schema 4 and remain compatible with schema 3 clients. The embedding revision remains unchanged, preserving vector compatibility. Answer-accuracy and performance thresholds are outside the selected release claim.
Refs #2536.