Bump Logbook version to 3.0.0 #1448
Merged
Conversation
This file contains 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
msdousti
requested review from
whiskeysierra,
lukasniemeier-zalando,
fatroom,
Semernitskaya,
dingxiangfei2009,
Joyfolk and
gpradeepkrishna
as code owners
|
Thank you for the contribution! |
|
👍 |
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.
Bumped Logbook version, and applied required changes to
imports.Description
Three changes were applied:
logbook-coremodule is moved from packageorg.zalando.logbooktoorg.zalando.logbook.core. Two tests needed an adjustedimport.2.7.9(security vulnerability) to2.7.12to make tests pass.Motivation and Context
New Logbook comes with a lot of bug-fixes and features.
Types of changes
It won't be a breaking change, unless Logbook dependency is transitively used by a project that uses Riptide.
Checklist: