ci: add manually triggerable beta release workflow#61
Merged
Conversation
Extract the beta release pipeline into a new reusable workflow that can be invoked both manually from the GitHub UI and from on_master.
vdusek
added
t-tooling
janbuchar
approved these changes
May 4, 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
3 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
release_prepare→changelog_update→pypi_publish) fromon_master.yamlinto a newmanual_release_beta.yamlreusable workflow.workflow_dispatch(manual trigger from the GitHub UI) andworkflow_call(soon_mastercan keep auto-publishing betas after master pushes).on_master.yamlnow has a singlebeta_releasejob that calls the new workflow, preserving the existing skip condition (!ci/!docs/!test+apify/org gate) andcode_checks+testsdependencies.Why
We previously had no way to cut a beta without pushing a release-triggering commit to master. With this change, a beta can be released on demand from the Actions tab, while the existing automatic flow on master is preserved.
Mirrors apify/apify-sdk-python#886.