docs(deps): fold the two NexusKit comments into one - #37
Merged
Conversation
They had drifted apart: the second still explained why Sync sat a patch ahead of the others, which stopped being true when all five moved to 0.5.1. What is left is the rule that outlives any particular version — they move together because NexusKit publishes them together, and the ranges stay open-ended. Sync joins the list in alphabetical order rather than trailing it; there is no longer anything special about that line.
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
1 participant
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.
Comment-only. No version changes.
The block had grown two comments that no longer agreed. The second explained why
NexusKit.Syncsat a patch ahead of the others — true for about twenty minutes, and false since #36 moved all five to0.5.1. A comment describing a state that no longer exists is worse than none: the next reader trusts it.What is left is the part that outlives any particular version:
NU1603— the failure this repository already hit once.NexusKit.Syncit is worse than inconvenient: pinning the protocol is how a client ends up unable to follow a server that has moved on.NexusKit.Syncalso joins the list alphabetically instead of trailing it. There is nothing special about that line any more.