docs: §4.2 release-doc sweep — bump install coords 0.2.0 → 0.4.0#202
Merged
Conversation
Every copy-pasteable install coordinate in published docs now reads
the current released baseline (0.4.0) instead of the long-stale
0.2.0:
- README quick-start
- docs/intro/install.md (umbrella + per-module + testkit)
- docs/guide/{terminal,screen,app,widgets,testing}-layer.md
- docs/tut/01-hello-world.md
- docs/reference/api.md (module table)
Migration notes (docs/reference/migration.md) acknowledge
0.2.0 / 0.3.0 / 0.4.0 → 1.0 as the no-migration window, and the new
reduced-motion entry is catalogued.
Roadmap headline updated: 2026-05-01, current release 0.4.0, §3.6 DoD
clean except for the §4.2 entry which is now also closed (interim
0.4.0 pass; the final 0.4.0 → 1.0.0 mechanical bump rides with the
release PR itself). §2 "Current state" heading + docs-site counts
also refreshed.
Historical mentions of 0.2.0 / 0.3.0 in migration / roadmap text are
kept — they describe the pre-1.0 cycle in context.
With this and PR #201 (§3.3) merged, all of §3 + §4 of the 1.0
roadmap is closed. 1.0-RC1 is unblocked.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…ep-42 # Conflicts: # docs/contrib/ROADMAP.md
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.
Summary
Closes §4.2 (Version & release-doc sweep). Every copy-pasteable install coordinate in the published docs now reads the current released baseline (
0.4.0) instead of the long-stale0.2.0:README.mdquick-startdocs/intro/install.md(umbrella + per-module + testkit)docs/guide/{terminal,screen,app,widgets,testing}-layer.mddocs/tut/01-hello-world.mddocs/reference/api.mdmodule tableMigration notes (
docs/reference/migration.md) now acknowledge0.2.0 / 0.3.0 / 0.4.0 → 1.0as the no-migration window, and the new reduced-motion entry is catalogued.Roadmap refresh:
Status: 2026-05-01 · Current release: 0.4.0, with the new "what's left for 1.0" framing.0.4.0 → 1.0.0bump rides with the release PR).☐ticked.Historical mentions of
0.2.0/0.3.0are kept in context (early-semver example in README, pre-1.0 cycle catalogue inmigration.md, migration story in §3.5 / §4.7) and explained as intentional in §4.2 itself.With this and PR #201 (§3.3) merged, all of §3 + §4 of the 1.0 roadmap is closed and 1.0-RC1 is unblocked.
Test plan
mdbook buildclean (linkcheck no errors)% "0.2.0"or:0.2.0install coordinates in the published docs0.2.0/0.3.0mentions are intentional and contextualciChecknot needed