Repository navigation
chore(deps): refresh compatible Java dependencies and build plugins - #25
Merged
Merged
Conversation
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
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.
Refresh compatible Jackson, SnakeYAML and Maven build/test plugins. Keep stable protobuf, AssertJ, JUnit and the existing Java 17 baseline; prerelease and major upgrades are excluded.
Validation: full mvn verify passes, including fake-engine integration and coverage thresholds; the SDK installs locally and every example compiles. The six Java 17/21 platform CI jobs remain required.
The example SDK installation now runs unit tests as well as integration tests before checking coverage. The previous command skipped the unit tests but still enforced combined coverage; the 70% threshold is unchanged. A clean install and all ten example builds pass locally.