ci: rename publish env from public-sdk to publish#551
Merged
Conversation
Aligns the python publish workflow with the env name used by all other workflows. The public-sdk environment no longer exists on the repo (removed when renaming to publish), so the publish workflow currently references a non-existent environment.
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 publish workflow references an environment called
public-sdkthat no longer exists on the repo (verified via API). All other workflows in the repo usepublishas the env name.Fix
One-line rename in
.github/workflows/sdk_publish_mistralai_sdk.yaml:Why this matters
Without this fix, the publish workflow either fails or skips the required reviewer gate entirely when triggered on push to main, defeating the env-scoping setup.