Fix release candidate logic #729
Merged
+10
−6
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
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.
Summary & motivation
This fixes three issues:
--no-git-tag-versiondoesn't create commits in addition to tags, so we switch back to using the flag for all new versions and filter onrcbeing in the commit name--tagflag should be onyarn publish, not onyarn versionBecause of (2), the
latesttag was incorrectly pointing to 5.9.2-rc.0 for about 5 minutes until I manually fixed the tag. Because this was a no-op change, there should be no real issues. However, anyone upgrading to latest at that time might be surprised with the release candidate version.Testing & documentation
Once merged, I will run another release candidate publish to verify the state of the system.