Repository navigation
release(1.5.0): the custom response modifier and the engine floor guard-core-go v4.4.0 - #44
Merged
Merged
Conversation
…rd-core-go v4.4.0
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 #43
I raised the engine floor to
guard-core-go/v4 v4.4.0and prepared the v1.5.0 release entry. The release also carries theCustomResponseModifierfix already on master. No adapter code changed.What ships
go getplusgo mod tidy; onlygo.modandgo.summove).::ffff:clients, a whitelist decides alone, dynamic rule versions no longer stack, and the scan budgetpattern_timeout.Version choice
Minor, not patch: the floor moves to a new engine minor with behavior changes that reach adapter users through MVS. The exported API of the root package is identical to v1.4.0 (
go doc -alldiff is empty), so no/v2path is involved.Gates (go1.26.5, Redis on 6379)
gofmt, go vet, staticcheck, go test, go test -tags integration, the 100% coverage gate and govulncheck (go1.27.2) all exit 0. I will tag v1.5.0 after merge; the tag is the release.