docs: record 1.0.1 in the file that records releases - #189
Merged
Conversation
- the roadmap declares itself the record of what a release contained, and 1.0.1 was in its table with no entry behind it - say what the patch carried, and that the settings freeze 1.0.0 declared held through it - add a section for the state after it: nothing is planned, which is the state rather than an omission, and name the three things that would justify the next release
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.
docs/roadmap.mdopens by saying it is where a release's contents are recorded.1.0.1 was in its table and had no section behind it — 0.4.0, which was also
unplanned, has one, so the convention was there and this release had fallen
through it.
rather than the changelog: the settings freeze 1.0.0 declared held through it.
left as a blank, with the three things that would justify the next release: a
defect found in use, a Tistory change the skin has to answer, or a request
from someone running it.
Also, outside this diff: the repository description was replaced with the
README's opening sentence. The old one ran long enough that GitHub's own
generated card truncated it mid-clause, and now that the social card carries no
sentence of its own, that description is the text a reader actually gets beside
the image.
Validation
node scripts/check.mjs— 25 checks, passed.