CI - Stop master releases using existing version numbers #1119
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
Aidan63
changed the title
|
Update: Seems like it will fail instead of overwrite when it uses the same version number, which is good. |
Aidan63
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.
The counter the CI release logic uses was reset when I moved the yml to a different workflow file so the last two master commits have overwritten previous github releases... I've worked around it in this by just adding a number larger than the latest pre-github CI merge.
As mentioned in the block comment, this will need to be looked at again when we want anything other than the last build number to increase.
@Simn