The release team wants to be able to trigger and coordinate version-bump automation across all relevant components, including Cloudbeat. Their plan is to add a Buildkite pipeline in each repo that will handle this automation.
After our meeting with @jmlrt, one of the proposed actions is that the BK pipeline will trigger our existing version-bump GitHub Action, which today is triggered manually.
Note that this action covers major and minor releases, while patch releases are currently handled by a bot maintained by the ingest team.
It might be worth retiring the patch-release bot and moving to a single, unified flow for version bumps.
To support that, we could update our GitHub Action so it can handle patch bumps without creating the integration PRs.
Relevant links:
The release team wants to be able to trigger and coordinate version-bump automation across all relevant components, including Cloudbeat. Their plan is to add a Buildkite pipeline in each repo that will handle this automation.
After our meeting with @jmlrt, one of the proposed actions is that the BK pipeline will trigger our existing version-bump GitHub Action, which today is triggered manually.
Note that this action covers major and minor releases, while patch releases are currently handled by a bot maintained by the ingest team.
It might be worth retiring the patch-release bot and moving to a single, unified flow for version bumps.
To support that, we could update our GitHub Action so it can handle patch bumps without creating the integration PRs.
Relevant links: