ci: remove standalone azure and gcp PyPI publish steps#554
Merged
Conversation
The Python release model publishes a single mistralai package to PyPI. That root wheel already bundles the Azure and GCP clients, so the workflow should not attempt to publish mistralai-azure or mistralai-gcp as standalone PyPI projects. Removing those extra publish steps keeps the workflow aligned with the actual release model and avoids failing after the real package has already been published.
louis-sanna-dev
approved these changes
May 25, 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.
Summary
The Python release model publishes a single
mistralaipackage to PyPI. That root wheel already bundles the Azure and GCP clients, so the workflow should not attempt to publishmistralai-azureormistralai-gcpas standalone PyPI projects.Fix
Remove the standalone Azure and GCP build/publish steps from
sdk_publish_mistralai_sdk.yaml, leaving only the bundledmistralaipublish path.Why
Keeping the extra publish steps makes the workflow fail after the real package has already been published, which creates noise and does not match how the package is meant to ship.