ci: add two-step GitHub release and PyPI publish workflows#712
Merged
Conversation
Adopt the mostlyai-qa release flow by adding a manual GitHub release bump workflow and a follow-up PyPI publish workflow triggered on successful release completion. Made-with: Cursor
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
release-1-bump.yamlto bump version, create/merge a release PR, and create a GitHub release tagrelease-2-publish.yamlto build and publish the package to PyPI after successful step 1 (or via manual dispatch)mostlyai/sdk/__init__.py) and.yamlconventionsTest plan
Release Step 1 - Release on GitHubwith a test versionRelease Step 2 - Publish to PyPItriggers after step 1 successworkflow_dispatchagainst a safe refMade with Cursor