Repository navigation
Open the 2.5 cycle - #650
Merged
Merged
Conversation
Release checklist steps 8 and 9 after 2.4.0 shipped: DEFAULT_BASELINE moves to 2.4.0 and expected_since_2.4.0.toml opens empty, enrolled in all six filename rosters (four in test_ledger_guards.py, two in compare.py); the 2.3.0 rows' "open cycle" comments now say "2.4 cycle". VERSION is (2, 5, 0) with PRE_RELEASE "dev", and the release log has a 2.5.0 Unreleased entry. CITATION.cff stays at 2.4.0 by design. The default-baseline run reads 0 intentional, 0 unexplained against the published 2.4.0 wheel, as a fresh cycle should. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #650 +/- ##
=======================================
Coverage 99.02% 99.02%
=======================================
Files 46 46
Lines 4513 4513
=======================================
Hits 4469 4469
Misses 44 44 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Release checklist steps 8 and 9, after 2.4.0 reached PyPI:
DEFAULT_BASELINEmoves to2.4.0, andtools/differential/expected_since_2.4.0.tomlopens empty, using Open the 2.4 cycle #526's template with the versions advanced. It is enrolled in all six filename rosters:_SPAN_BEARING_RULES,_CORPUS_CLAIMS,_CROSS_RULE_WINNERSand_ORDER_EXEMPTION_EFFECTin the test module, plus_RECORDED_DIFFSand_WATCHED_DIFFSin compare.py. The 2.3.0 rows' "open cycle" comments now say "2.4 cycle".VERSION = (2, 5, 0),PRE_RELEASE = "dev", so__version__is2.5.0dev. The release log gets a2.5.0 - Unreleasedentry.CITATION.cffstays at2.4.0. It names the last released version on purpose.Step 7 is already done: milestone 2.4 is closed. There is no 2.5 milestone yet; create one when you want one.
Test plan
compare.pyat the default baseline exits 0 with 0 intentional and 0 unexplained diffs against the published 2.4.0 wheel🤖 Generated with Claude Code