Bump io.swagger:swagger-codegen to 2.4.16 #143
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
macisamuele
force-pushed
the
maci-bump-codegen
branch
from
687be6b
to
e6960cd
Compare
Codecov Report
@@ Coverage Diff @@
## master #143 +/- ##
=========================================
Coverage 71.95% 71.95%
Complexity 139 139
=========================================
Files 11 11
Lines 574 574
Branches 75 75
=========================================
Hits 413 413
Misses 118 118
Partials 43 43 Continue to review full report at Codecov.
|
|
Ps.the title is inaccurate...the bump is to patch 16 |
cortinico
approved these changes
Oct 25, 2020
cortinico
changed the title
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.
As the title says.
The goal of this is to prepare a branch to address the addition of OpenAPI v3 (#51) and ideally we might (even if I doubt) reduce some conflicts.
Still bumping a dependency is not a bad idea, especially if tests continue to be green