Repository navigation
release(4.4.0): scan budget and IP parity release, lockstep core engines at 4.4.0 - #90
Merged
Merged
Conversation
…nes at 4.4.0 (#89) Writes the 4.4.0 CHANGELOG section. The PHP package carries no version file, so the v4.4.0 tag is the version Packagist publishes.
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.
Closes #89
I ran
make bump-version VERSION=4.4.0, which only scaffolds the CHANGELOG because PHP has no version file (Packagist takes the version from the tag), and filled the 4.4.0 section from the PRs merged since v4.3.3 (#73 to #88).Breaking changes called out in the CHANGELOG:
enableDynamicRulesandenableEnrichmentnow requireenableAgent, and a configured whitelist now decides alone (IP list precedence). New for adapters:GuardEngine::applyResponseModifier(). Also covered: client identity parity with the reference, dynamic rules applied over the base config, the scan time budget, and the per-pair Cookie scan.Gate on this branch, run the way ci.yml runs it against a private Redis (never 6379):
make lint,make test, every runner in the ci.yml test and conformance jobs, the pcov coverage gate (99.18% lines, every executable line covered or provably unreachable) andcomposer audit --lockedall exit 0. I did not tag or release.