docs(changelog): record the compatibility gate in 3.2.0 - #432
Conversation
The 3.2.0 section described the unified sports library but none of the install-path work that landed in #428 and #431 -- which matters more than a normal changelog omission, because the sunset rule keys on this section to tell plugin authors what a given floor buys them. The headline addition: 3.2.0 is the first release that *enforces* ledmatrix_min_version. Before it the floor was advisory, so a plugin could declare one and still be delivered to a core that could not run it. That is the property B6 waits on, and it is now stated where a plugin author will look for it -- along with the caveat that a core reporting below 2.0.0 is treated as unknown rather than old and is never blocked. Also records compatibility.py (and that it does not yet read compatible_versions), check_release_version.py and its workflow, the install-preservation fix, the reentrant-lock deadlock fix, and the web_interface version re-export. No version bump: 3.2.0 is unreleased, so this describes the release being cut rather than a new one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Udr6MfaFLUPhX5Fgo67Jf5
|
Warning Review limit reached
Next review available in: 23 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Landed directly on |
Up to standards ✅🟢 Issues
|
Last step before tagging v3.2.0. Documentation only, no version bump — 3.2.0 is unreleased, so this describes the release being cut rather than a new one.
Why this isn't a routine changelog omission
The 3.2.0 section described the unified sports library but none of the install-path work from #428 and #431. That matters more than usual here, because the sunset rule keys on this section to tell plugin authors what flooring at a given version actually buys them.
The headline addition:
That is precisely the property B6 waits on, and it now sits where a plugin author will look for it — including the consequence that B6 waits for 3.2.0 to be widely installed, not merely released.
It also records the deliberate exception, which is easy to mistake for a bug later: a core reporting below
2.0.0is treated as unknown rather than old and is never blocked, because v3.1.0 ships__version__ = "1.0.0"while nearly every manifest floors at2.0.0.Also recorded
src/plugin_system/compatibility.py— and explicitly that it does not yet readcompatible_versions, the schema-required field that can express upper boundsscripts/check_release_version.py+ theRelease version checkworkflow, with the reason it exists (v3.1.0 tagged six weeks before the version string was bumped)web_interface.__version__re-exportVerified
test_version_consistencypasses (5), andscripts/check_release_version.py v3.2.0reports tag, CHANGELOG andsrc.__version__all agree against this tree.🤖 Generated with Claude Code
https://claude.ai/code/session_01Udr6MfaFLUPhX5Fgo67Jf5