Feature/version bump workflows #511
Merged
Conversation
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
Applied prettier formatting to workflow files and documentation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Version bumps are now managed via GitHub Actions. Kept only utility targets: show-versions and dry-run testing. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This pull request migrates the Python package version bumping process from Makefile commands to GitHub Actions workflows. Now, each package can be bumped directly from the GitHub UI via workflow_dispatch, with clickable links provided in
Development.md. The Makefile bump targets are kept for local testing only, and rollback instructions are included in the documentation. The implementation follows a reusable workflow pattern for maintainability.Version Bump Automation
.github/workflows/bump-version-reusable.yml) that handles version bumping for any Python package usingbump2version, automatically committing and pushing changes to the main branch.cua-core,cua-computer,cua-agent,cua-som,pylume,cua-computer-server,cua-mcp-server) that invoke the reusable workflow with appropriate parameters. [1] [2] [3] [4] [5] [6] [7]Documentation Updates
Development.mdto provide workflow links for each package, step-by-step usage instructions, rollback procedures, and tag naming conventions. The Makefile approach is now marked as for local testing only.Makefileclarifying that Makefile bump targets are deprecated for production releases and should only be used for local testing.Design Documentation
docs/plans/2025-10-25-version-bump-workflows-design.md) describing the rationale, requirements, workflow architecture, error handling, and migration strategy for the new version bump process.