Repository navigation
docs: record 0.2.2 and 0.2.3 - #30
Merged
Merged
Conversation
Two releases shipped while the changelog still had 0.2.2's work sitting under Unreleased and no mention of 0.2.3 at all. Dates added to every release. The 0.2.2 note is rewritten in the past tense: it warned that one more upgrade would still stop the service, and that upgrade has now happened.
Merged
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 changelog still had 0.2.2's work under
## Unreleased, and 0.2.3 was missing entirely. Two releases behind.Unreleasedbecomes0.2.2, dated0.2.3entry for the reload fix (Hot reload leaves the old routing partly live #26)UnreleasedThe 0.2.2 note is rewritten in the past tense. It used to warn that one more upgrade would still stop the service; that upgrade has since happened, so the warning now reads as history rather than as something to watch for.
The 0.2.3 entry leads with the symptom rather than the cause, since the symptom is what anyone would recognise:
Also filed from today's session, not fixed here: #28 (IPv6-only dev servers get a silently dead route) and #29 (multi-label bare names are not suffixed).