Prepare Python SDK release automation#318
Merged
Merged
Conversation
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
1 participant
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
maintarget_commitishMotivation
The monorepo SDK release orchestrator must be able to wait for CI on Fern-generated pull requests and publish a release from the exact merged commit. GitHub release
target_commitishis metadata and is not a reliable release-integrity gate; the workflow already checks out the release tag and verifies that its version matchespyproject.toml.Validation
actionlint .github/workflows/ci.yml .github/workflows/release-cloud.ymlgit diff --checkImpact
No SDK runtime code changes. This prepares the Python repository for orchestrated SDK releases.