Repository navigation
chore(engine): pin guard-core-jvm to db716ec - #25
Merged
Merged
Conversation
Moves the engine ref in CI, CodeQL, release, settings and docs from 09dfddf to db716ec, which carries the detection scan budget and the dynamic rules overlay. Closes #24
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 #24
I moved the guard-core-jvm engine pin from 09dfddf to db716ec in the three workflows, settings.gradle.kts, README, CONTRIBUTING, docs and examples/demo-boot, and added a CHANGELOG entry. Same change as Guard-Core/ktor-guard#18.
I verified locally with the composite build against the engine at db716ec: spotlessCheck, detekt and build pass (43 tests, 0 failures).