Repository navigation
release(4.4.0): Engine routing parity with fastapi-guard - #41
Merged
Merged
Conversation
github-actions
Bot
added
documentation
guard-core 4.4.0 is on PyPI, so the floor moves up and upgrading this adapter brings the engine fixes. The release notes say so instead of asking users to upgrade guard-core separately.
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 commit for 4.4.0: carries the engine routing parity fix (#40: passthrough, route bypass and the response pass through the engine like fastapi-guard, a request with no client address answered 403 under the default
fail_secure, no request metrics for blocked, preflight and bypass responses, global behavioral return rules run) and the housekeeping merged since 4.3.3. Version bump, changelog, release notes, mike/versions.json and the example image tag.The version is a minor because the adapter has its own line (4.2.0 and 4.3.0 were minors for behavior changes, 4.3.1 to 4.3.3 patches) and no public API changed. The
guard-corefloor stays at>=4.1.0, so the guard-core 4.4.0 fixes arrive by upgrading guard-core.Nothing is tagged or released by this PR.