Repository navigation
fix(v0.7.72): recompute structure hash on settlement, relocate without region cache, release update lock - #71
Merged
Merged
Conversation
…t region cache, release update lock Co-authored-by: Cursor <cursoragent@cursor.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
knowledge/structure.yamlinput hash after citations are rewritten, soverifyno longer reports a stale structure. A structure that was already stale stays stale for Close.updatewith explicitprocessed_versionno longer leaves the write lock behind when the checkout differs from the pinned ref.repo-content:citations changed or cannot be confirmed are listed inreference_warnings; settlement rules are unchanged.Verification
bun run build,bun run verify:fullbun run release:prepare(13 packages at 0.7.72)