Repository navigation
chore(engine): move the pinned guard-core-jvm ref to db716ec - #18
Merged
Merged
Conversation
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 #17
I moved the engine pin in ci.yml, code-ql.yml and release.yml from 9067b7b to db716ec (current guard-core-jvm master, full SHA in the workflows), and updated the references in settings.gradle.kts, CONTRIBUTING.md, docs/installation.md, docs/examples.md and the changelog. This follows the same pattern as spring-boot-guard #23.
Verified locally with the composite build pointing at db716ec:
./gradlew build --no-daemonexits 0 with 37 tests, 0 skipped, 0 failures, Redis on 6379.