RET2-2: add Python release-please workflow#445
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
Adds the production release-please workflow for the Python SDK and a conservative auto-merge workflow for machine-generated SDK release PRs.
release-please.ymlusesRELEASE_PLEASE_TOKENso release-created events can trigger the existing PyPI publish workflow.stlc-auto-merge.ymlauto-merges only qualifying automated PRs when all head-sha checks are completed and green.stainless/releasesync PRs use merge commits so conventional generated SDK commits are preserved for release-please.Secrets needed
RELEASE_PLEASE_TOKENinRetellAI/retell-python-sdkNo secret values are included in this PR.
Linear: RET2-2