chore(release): v0.8.2 — timing-flake fix#44
Merged
Conversation
Bumps version 0.8.1 → 0.8.2 and finalizes the CHANGELOG section for the test-fixture timing fix that landed on main in PR #43. Cutting a patch release rather than carrying [Unreleased] forward: the fix surfaced during the v0.8.1 release flow, was framed as "pre-existing" at the time, and shipped past — bundling it into a future release would repeat the deferred-fix pattern v0.8.1's own changelog called out. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
0.8.1→0.8.2inpyproject.tomland__init__.py.CHANGELOG.mdsection — moves the timing-flake fix entry from[Unreleased]to[0.8.2] - 2026-05-03and adds the comparison link.Why a v0.8.2 patch instead of bundling into the next release
The fix landed on main in PR #43 as
[Unreleased]. I initially proposed deferring the release until other work accumulated — that's exactly the deferred-fix pattern v0.8.1's own changelog called out for the per-module coverage rot. The fix surfaced during the v0.8.1 release flow and shipped past it; cutting v0.8.2 immediately ships it cleanly and keeps the journal-entry rule honest.Test plan
scripts/ci-local.shpasses (matrix profile, isolated.venv-ci/, 1952 tests, all coverage floors)pyproject.toml0.8.2,__init__.py0.8.2, CHANGELOG[0.8.2]section + comparison link🤖 Generated with Claude Code