Repository navigation
release(1.2.0): stream responses and evaluate body return patterns - #36
Merged
Merged
Conversation
Version 1.2.0. Responses stream unbuffered unless a body feature is active, so the guard no longer sets Content-Length on streamed responses, and body based return_pattern rules evaluate. The Unreleased changelog section becomes 1.2.0. The engine stays at guard-core 4.4.0.
The docs index still said 1.0.0 and engine 4.3.3, and several install and build comments named the engine at 4.3.3. They now match guardCore 4.4.0 and this release.
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
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.
Closes #35
version1.1.0 to 1.2.0, install snippets to 1.2.0.[1.2.0] - 2026-10-17.Local gate:
./gradlew spotlessApply detekt build --no-daemon --max-workers=20 with Redis on 6379, and no files changed by spotlessApply.