Automatically suffix the README version after a release#422
Open
savannahostrowski wants to merge 2 commits into
Open
Automatically suffix the README version after a release#422savannahostrowski wants to merge 2 commits into
savannahostrowski wants to merge 2 commits into
Conversation
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
1 participant
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.
Closes #169
Opted to automatically update the README (rather than remind), using option 1 from the discussion: This is Python version 3.15.0 beta 3+dev style suffixes. This happens in release.py --done, alongside the existing patchlevel.h update, so it lands in the post-release commit: + for 3.14 and earlier, +dev for 3.15+.