No latest tag until a latest tag is published #140
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
With the current setup, when you are first pushing releases with a --tag=rc for example, sinopia insists that there is a latest tag. I believe checking for the igore_latest_tag is enough to get the old sinopia behavior back. No need to add the latest dist-tag if non latest version was added.
|
There is always a latest tag. Otherwise So it's kinda intended. What issues does it cause? |
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.
With the current setup, when you are first pushing releases with a --tag=rc for example, sinopia insists that there is a latest tag.
I believe checking for the igore_latest_tag is enough to get the old sinopia behavior back. No need to add the latest dist-tag if non latest version was added.