Repository navigation
release(4.4.0): scan budget and IP parity release, lockstep core engines at 4.4.0 - #144
Merged
Merged
Conversation
…nes at 4.4.0 (#143) Bumps all five packages to 4.4.0 and writes the 4.4.0 CHANGELOG section. The two engine-version literals in the validation-cache and agent-config tests move with the bump.
github-actions
Bot
added
documentation
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 #143
I bumped all five packages (
@guardcore/core, express, fastify, hono, nestjs) and the private root to 4.4.0 withmake bump-version VERSION=4.4.0, and wrote the 4.4.0 CHANGELOG section from the PRs merged since v4.3.3 (#130 to #142). The two engine-version literals in the validation-cache and agent-config tests move with the bump.Behavior changes called out in the CHANGELOG: adapters reach the real handler for excluded, bypass and addressless requests, canonical client identity, a configured whitelist decides alone, route country verdict combination, unknown identity and ungeolocated clients, the scan time budget, and dynamic rules applied over the base config.
Gate on this branch:
pnpm build,pnpm lint,pnpm test,pnpm test:coverage(reports for all five packages) and the conformance run all exit 0, andpnpm audit --audit-level=lowwas run. I did not tag or release.