Skip to content

[docs]: Support the two minors before 1.0 for critical fixes - #239

Merged
pseudomuto merged 1 commit into
mainfrom
readme-support-window
Oct 16, 2026
Merged

pseudomuto merged 1 commit into
mainfrom
readme-support-window

Conversation

@pseudomuto

Copy link
Copy Markdown
Collaborator

The README said critical fixes reach the latest release and the two before it only when each is 1.0 or later, so no 0.x line would get a patch after 1.0 ships. CONTRIBUTING describes the intended policy: the current minor and the two before it, whatever their major version.

The README now matches CONTRIBUTING, and both use the lines that will actually be supported once 1.0 is out (v1.0, v0.10, and v0.9) as the example. CONTRIBUTING previously skipped v0.10.

The README said critical fixes reach the latest release and the two
before it only when each is 1.0 or later, so no 0.x line would get a
patch after 1.0 ships. CONTRIBUTING describes the intended policy: the
current minor and the two before it, whatever their major version.

The README now matches CONTRIBUTING, and both use the lines that will
actually be supported once 1.0 is out (v1.0, v0.10, and v0.9) as the
example. CONTRIBUTING previously skipped v0.10.
@pseudomuto
pseudomuto requested a review from a team as a code owner October 16, 2026 19:58
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@pseudomuto
pseudomuto merged commit 33879c3 into main Oct 16, 2026
6 checks passed
@pseudomuto
pseudomuto deleted the readme-support-window branch October 16, 2026 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants