docs: define strict_http compatibility lifecycle (#309) - #332
Merged
Conversation
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.
Why
strict_http=Falseis documented as a temporary compatibility mode, but the project does not currently say how long it will remain supported.This makes the 1.x compatibility policy explicit before the 1.1.0 release.
What
strict_http=Falseremains available throughout the 1.x release seriesstrict_http=Truebehavior and handleMlbHttpErrorTests
Documentation-only change.
Normal CI should still run before merge.
Risk and impact
Risk: Minimal
No runtime behavior or public signatures change. This PR only clarifies the existing compatibility policy.
Closes #309.