[PLAT-193] Fix python sdk publish to pypi gha#43
Merged
winnie-opal merged 1 commit intoApr 22, 2026
Conversation
elliot-opal
approved these changes
Apr 22, 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
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.

The publish to pypi workflow was silently broken and attempts to publish every release as 1.0.0 which gets skipped since it already exists.
The OpenAPI generator upgrade from 7.10.0 to 7.19.0 changed the pyproject.toml format from [tool.poetry] to the standard [project] table which causes the hardcoded
version = "1.0.0"to override the old versioning logic.See workflow run here https://github.com/opalsecurity/opal-python/actions/runs/24752948149/job/72419853149
This replaces that hardcoded
version = "1.0.0"to["version"]. This also updates the workflow to specifyfetch-tags: truein the checkout so the workflow can use the git tag for the version.Tested this locally to confirm that new builds use the existing tag