Upgrading dependencies and bumped to 1.2.1 #146
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
rjrudin
requested review from
BillFarber,
SameeraPriyathamTadikonda,
anu3990,
hansenmc and
jamesagardner
SameeraPriyathamTadikonda
approved these changes
Aug 18, 2022
BillFarber
approved these changes
Aug 18, 2022
anu3990
approved these changes
Aug 18, 2022
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.
I'm looking to do a 1.2.1 release that only upgrades dependencies so that they're in sync with the ml-gradle stack. The driving use case is I want to start using marklogic-junit5 for tests in the Kafka connector project and I'd like to have the same versions of all Java Client / Spring / etc dependencies.