Repository navigation
chore(engine): pin guard-core-jvm to 6cde4af - #27
Merged
Merged
Conversation
Moves the pinned engine ref from db716ec to 6cde4af (guard-core-jvm master, the 4.4.0 line) in CI, CodeQL, the release build, settings and the docs, so CI tests the engine code that ships in 4.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 #26
I am moving the pinned guard-core-jvm ref from db716ec to 6cde4af (guard-core-jvm master after #57, the 4.4.0 line) in ci.yml, code-ql.yml, release.yml, settings.gradle.kts, CONTRIBUTING, README, the docs and the demo-boot example, so CI tests the engine code that ships in 4.4.0. The lockstep
guardCoreversion in gradle/libs.versions.toml stays 4.3.3 until 4.4.0 is on Maven Central: the release build runs with composite off and resolves that coordinate from Central, so an unpublished version would fail it.Gates run locally against the engine at the 4.4.0 bump:
./gradlew spotlessApply detekt(exit 0) and./gradlew build --no-daemon(exit 0). I am not tagging or releasing.