Repository navigation
docs: clarify 0.11.0 upgrades and verified V2 behavior - #79
Merged
Merged
Conversation
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.
The README still described timed reclamation of quiet live lease owners, although 0.11.0 explicitly disposes the previous same-process V2 instance before replacement. Correct that explanation and remove the duplicate lease paragraph.
Add 0.11.0 upgrade instructions, the verified V2 Plan/audit/reload behavior, and the host limitation that retains verifier child sessions. Update the compatibility table to reflect acceptance of the final release tarball.
Validation: all six README JSON examples parse, V1/V2 version pins and relative Markdown link targets verified, and
git diff --checkpasses. Documentation only; no runtime changes. npm latest is confirmed as 0.11.0 with the digest of the tested artifact.