Fetch the correct version from PyPI in the release workflow - #200
Merged
Omar-V2 merged 1 commit intoAug 18, 2026
Merged
Conversation
gyang-xai
approved these changes
Aug 18, 2026
mark-xai
approved these changes
Aug 18, 2026
Omar-V2
deleted the
fix/fetch-correct-version-from-pypi-in-release-workflow
branch
August 18, 2026 18:52
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
3 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.
In the release workflow, the step which fetched the latest package version from PyPI was broken, this uses the correct field from the response returned PyPI to make sure the variable always captures the latest package version, which is then used to compare to the current version which is being publshed.