Open
Conversation
| "1.1.0.dev3+h000000000000": { | ||
| "latesttag": "1.0", | ||
| "latesttag": "1.0.0", | ||
| "latesttagdistance": "3", |
Contributor
There was a problem hiding this comment.
i need some more examples, i cant quite wrap my head around it
this is a orkaround to ease the pain, but its also unable to completely prevent it
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
2 participants
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.
Using the
release-branch-semverscheme, a commit five nodes off e.g.1.0.0will get1.1.0dev5, but a commit four nodes off1.0.1will get1.1.0dev4, despite it being more commits from1.0.0. To fix this, we add a factor that we use for bumping the distance based on the micro release we're discarding. The default is1000; for most projects, that should be plenty of commits per bug-fix release.Fixes #1025.