Repository navigation
CI: Add an initial workflow to prepare a release - #124
Merged
Merged
Conversation
pniedzielski
force-pushed
the
ci/release-automation
branch
2 times, most recently
from
November 9, 2026 21:08
234a4e5 to
ba965d3
Compare
Contributor
Author
|
@hallfox Interested to hear what you think about this. I think we could do this on the main repo and the Java SDK too. |
pniedzielski
marked this pull request as ready for review
November 9, 2026 21:13
Contributor
Author
|
That PR has been merged, rebasing on top of main fixes previous CI failures. |
This patch adds a workflow that will eventually fully automate the process of making a new release of the BlazingMQ Python SDK. The ultimate vision is this: making a release will involve going to the Actions tab on GitHub, clicking the “Prepare Release” button and selecting the new version and the branch to release. This will create a PR that bumps the version number in the source code and runs towncrier to generate the release notes. Someone reviews the PR and merges it, which creates a tag, a GitHub release, and pushes a new version to PyPI. The workflow in this commit is just a skeleton workflow, which adds the button, does some minimal version string verification, and prints the diff it would generate with the version bump and with towncrier release notes. It only does this as a dry run, and does not generate the PR. Signed-off-by: Patrick M. Niedzielski <pniedzielski@bloomberg.net>
pniedzielski
force-pushed
the
ci/release-automation
branch
from
November 9, 2026 22:28
ba965d3 to
8a85af5
Compare
chrisbeard
approved these changes
Nov 10, 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
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.
This patch adds a workflow that will eventually fully automate the process of making a new release of the BlazingMQ Python SDK.
The ultimate vision is this: making a release will involve going to the Actions tab on GitHub, clicking the “Prepare Release” button and selecting the new version and the branch to release. This will create a PR that bumps the version number in the source code and runs towncrier to generate the release notes. Someone reviews the PR and merges it, which creates a tag, a GitHub release, and pushes a new version to PyPI.
The workflow in this commit is just a skeleton workflow, which adds the button, does some minimal version string verification, and prints the diff it would generate with the version bump and with towncrier release notes. It only does this as a dry run, and does not generate the PR.