docs: 0.1.2 release wording - #112
Merged
Merged
Conversation
…refresh the stale 0.1.0 sentences
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.
The version bump rewrote three prose sentences it should not have ("releases after v0.1.1" → now correctly "after v0.1.0", the docs/index.md verification line that named 0.1.1's delegation change as 0.1.2's). Also refreshes sentences still describing the 0.1.0 state: the FAQ's Maven Central "still to come" and release link, the offline jar/nupkg install examples, the README status paragraph (validation suite done, next items), and the connection-keywords intro now that Windows adds a second keyword.