chore: prepare the 2.8.0 release - #197
Merged
Merged
Conversation
Minor, not patch: the release adds public API — the growing open wait (`Config.wait_duration_backoff_multiplier`, `Config.wait_duration_in_open_max`) and the `unreachable_exceptions` set on `CircuitBreaker`, `Registry` and `Engine` (#194, #195). griffe reports no removals or signature changes against v2.7.0, and the new `ValueError` that refuses a backoff alongside a shared `Storage` cannot reach a caller who upgrades: the multiplier it guards ships in this same release, so no configuration written before it can trip the check. - Bump the package version from 2.7.0 to 2.8.0. - Move the current [Unreleased] changelog entries into [2.8.0] - 2026-09-01, in the Added-before-Fixed order every other section uses. - Update the changelog comparison links, and the release version and month on the comparison page. - Regenerate docs/llms-full.txt.
Contributor
|
Warning Review limit reachedNext included review available in 40 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
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 |
Contributor
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
Prepare the
2.8.0minor release.2.7.0to2.8.0.[Unreleased]changelog entries into[2.8.0] - 2026-09-01, in the Added-before-Fixed order every other section uses.docs/llms-full.txt.Minor, not patch: the release adds public API. #194 gives
Configan open wait that can grow —wait_duration_backoff_multiplierandwait_duration_in_open_max— and givesCircuitBreaker,RegistryandEngineanunreachable_exceptionsset, so aHALF_OPENprobe that never reached the dependency hands its slot back instead of deciding the round against it. #195 refuses, at construction, a backoff asked for alongside a sharedStorage, which the coordinated lane has no way to honour.Nothing an existing caller does stops working. The defaults keep the historical behaviour:
wait_duration_backoff_multiplieris1.0, so the wait stays constant until it is raised, and only the two httpx transports pass a non-emptyunreachable_exceptionsout of the box (PoolTimeout). The newValueErrorcannot reach a caller who upgrades either — the multiplier it guards ships in this same release, so no configuration written against2.7.0can trip it.The two changes are released together on purpose. Shipping the backoff without the guard would leave an option that reads as enabled and does nothing under a shared
Storage, and adding the guard afterwards would then be the breaking change.Checklist
uv run ruff format --checkanduv run ruff checkpassuv run mypy,uv run pyrightanduv run pyrefly checkpassdocs/) for user-facing changesCHANGELOG.md[Unreleased]updatedAdditional release checks: the package build passes (
interlock_cb-2.8.0),twine checkPASSED on both artefacts, and griffe reports theVERSIONattribute (2.7.0→2.8.0) as the only public difference — the backoff fields andunreachable_exceptionsare additions, so nothing is flagged as a breakage.Related issues
#194, #195