Repository navigation
Adopt the shared Cinchapi dependency BOM - #7
Merged
Merged
Conversation
CircleCI no longer runs version 2 configs, so no pipeline ran for this branch. Declare version 2.1 and keep the existing job and its branch behavior. Move any step-level context, which version 2.1 rejects, to the workflow, and replace retired images.
jtnelson
marked this pull request as ready for review
November 1, 2026 17:33
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.
Summary
Use one versioned policy for shared JVM dependencies. The project pins
com.cinchapi:cinchapi-bom:1.0.0and keeps its managed library declarationsversionless.
Behavior
The BOM supplies accent4j 1.18.4, Guava 33.5.0-jre, Gson 2.13.2, and JUnit
4.13.2 when those dependencies are present. Ordinary Gradle conflict resolution
allows higher explicit versions. Existing dependency scopes remain intact.
Dependency exclusion rules retain the platform constraints so versionless Guava
can resolve. The rules continue to exclude the same transitive libraries.
Consumers require the public BOM artifact supplied by
https://github.com/cinchapi/cinchapi-bom/pull/1.