Check for .0a0 for new version creation, not .a0 #163
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
This was referenced Feb 28, 2024
kaos
approved these changes
Feb 28, 2024
thejcannon
approved these changes
Feb 28, 2024
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.
Minor typo in the check for alpha versions meant it didn't trigger: it's intending to search for
2.x.0a0, i.e. first alpha version leading up to the first stable release in2.xseries... but missed the 0 between the.and thea.This explains (#162 (comment)): why we don't have a
versioned_docs/version-2.20directory despite #153 landing.This PR doesn't create that directory, just fixing the bug in the automation. I've retriggered the sync from this PR's branch to do that: #164