ci: add manually triggerable beta release workflow#886
Merged
Conversation
Extract the beta release pipeline into `manual_release_beta.yaml` with both `workflow_dispatch` (for manual triggers) and `workflow_call` (so `on_master` can keep auto-publishing betas), so that beta releases can be cut on demand without needing a release-triggering commit on master.
vdusek
added
adhoc
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #886 +/- ##
=======================================
Coverage 87.01% 87.01%
=======================================
Files 48 48
Lines 2942 2942
=======================================
Hits 2560 2560
Misses 382 382
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
janbuchar
approved these changes
May 4, 2026
vdusek
added a commit
to apify/crawlee-python
that referenced
this pull request
May 4, 2026
## Summary - Extract the beta release pipeline (`release_prepare` → `changelog_update` → `pypi_publish` → `doc_release_post_publish`) from `on_master.yaml` into a new `manual_release_beta.yaml` reusable workflow. - The new workflow exposes both `workflow_dispatch` (manual trigger from the GitHub UI) and `workflow_call` (so `on_master` can keep auto-publishing betas after master pushes). - `on_master.yaml` now has a single `beta_release` job that calls the new workflow, gated on the same `feat|fix|perf|refactor|style:` commit prefixes and on `code_checks` + `tests` passing. ## 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.
vdusek
added a commit
to apify/apify-client-python
that referenced
this pull request
May 4, 2026
## Summary - Extract the beta release pipeline (`release_prepare` → `changelog_update` → `pypi_publish` → `doc_release_post_publish`) from `on_master.yaml` into a new `manual_release_beta.yaml` reusable workflow. - The new workflow exposes both `workflow_dispatch` (manual trigger from the GitHub UI) and `workflow_call` (so `on_master` can keep auto-publishing betas after master pushes). - `on_master.yaml` now has a single `beta_release` job that calls the new workflow, gated on the same `feat|fix|perf|refactor|style:` commit prefixes and on `code_checks` + `docstrings_checks` + `tests` passing. ## 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.
vdusek
added a commit
to apify/apify-shared-python
that referenced
this pull request
May 4, 2026
## Summary - Extract the beta release pipeline (`release_prepare` → `changelog_update` → `pypi_publish`) from `on_master.yaml` into a new `manual_release_beta.yaml` reusable workflow. - The new workflow exposes both `workflow_dispatch` (manual trigger from the GitHub UI) and `workflow_call` (so `on_master` can keep auto-publishing betas after master pushes). - `on_master.yaml` now has a single `beta_release` job that calls the new workflow, preserving the existing skip condition (`!ci`/`!docs`/`!test` + `apify/` org gate) and `code_checks` + `tests` dependencies. ## 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.
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→doc_release_post_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, gated on the samefeat|fix|perf|refactor|style:commit prefixes and oncode_checks+testspassing.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.