Make the package versions consistent #714
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
Differences in Hector outputsHello, this is The current pull request's outputs do not differ from 3.0.0 (9aebf67). |
Codecov Report
@@ Coverage Diff @@
## master #714 +/- ##
=======================================
Coverage 79.72% 79.72%
=======================================
Files 61 61
Lines 5978 5978
=======================================
Hits 4766 4766
Misses 1212 1212 |
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 it was pointed out in the GMD editor's feedback, there are some inconsistent package versioning numbers. I am not quite sure how it happened but with this PR all the version numbers should be consistent and then we can do a release with the correct number/delete the release with the incorrect versioning number? @bpbond what do you think?