Allow version to optionally be manually set during release - #767
Merged
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
Author
|
/azp run |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Scott Carda (ScottCarda-MS)
changed the title
Scott Carda (ScottCarda-MS)
marked this pull request as ready for review
August 10, 2026 19:59
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Stefan J. Wernli (swernli)
approved these changes
Aug 10, 2026
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
2 participants
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.
Adds an optional input field to the release pipeline that allows the user to specify the version they are building. If the field is left blank, falls back to the automated process of determining the version based on the Azure feed. The input is validated and the format must match the build type.
This is needed as the Azure feed can be slow to sync with PyPi, and if multiple releases need to be done in quick succession, the automated process will fail by calculating the same version for multiple runs.