Skip to content

ci: wire cua-driver into release-bump-version workflow - #1364

Merged
f-trycua merged 1 commit into
mainfrom
wire-cua-driver-bump
Apr 23, 2026
Merged

ci: wire cua-driver into release-bump-version workflow#1364
f-trycua merged 1 commit into
mainfrom
wire-cua-driver-bump

Conversation

@f-trycua

@f-trycua f-trycua commented Apr 23, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds cua-driver to the CD: Bump Version workflow dropdown, matching how lume is wired.

After this lands, running gh workflow run "CD: Bump Version" -f service=cua-driver -f bump_type=minor will:

  1. Bump the version string in libs/cua-driver/Sources/CuaDriverCore/CuaDriverCore.swift from 0.0.1 to 0.1.0 via the new libs/cua-driver/.bumpversion.cfg.
  2. Commit + push a cua-driver-v0.1.0 tag.
  3. The existing cd-swift-cua-driver.yml workflow (triggered by tags matching cua-driver-v*) then runs the codesign + notarize + GitHub-release flow.

Changes

  • .github/workflows/release-bump-version.yml:
    • Adds cua-driver to the service choice list (next to lume).
    • Adds the case branch mapping cua-driverlibs/cua-driver.
    • Adds a Capture bumped cua-driver version step mirroring the lume one.
  • libs/cua-driver/.bumpversion.cfg (new): current_version 0.0.1, tag pattern cua-driver-v{new_version}, bumps the public static let version string in CuaDriverCore.swift.

Test plan

  • After merge, run gh workflow run "CD: Bump Version" -f service=cua-driver -f bump_type=minor
  • Verify the workflow succeeds (bump commit + cua-driver-v0.1.0 tag pushed to main)
  • Verify cd-swift-cua-driver.yml fires on the new tag and produces a signed, notarized GitHub release

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Improved release automation to support version management for the cua-driver service, including automatic version bumping, release tagging, and consistent version tracking during deployments.

Adds cua-driver as a selectable service in the CD: Bump Version
workflow, matching how lume is wired. Running the workflow with
`service=cua-driver` now:

1. Bumps the version string in
   `libs/cua-driver/Sources/CuaDriverCore/CuaDriverCore.swift`
   (the single authoritative source read by TelemetryClient et al.)
   via the new `libs/cua-driver/.bumpversion.cfg`.
2. Creates and pushes a `cua-driver-v{new_version}` tag.
3. The existing `cd-swift-cua-driver.yml` workflow picks up the
   tag and runs the codesign + notarize + GitHub-release flow.

Current version is 0.0.1; first bump should be `minor` to reach
0.1.0 to match the public v0.1 release.

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel

vercel Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Apr 23, 2026 7:30am

Request Review

@coderabbitai

coderabbitai Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 544487ae-05f9-44f9-bbac-278f7e6a9bbd

📥 Commits

Reviewing files that changed from the base of the PR and between 9bb952c and 17f2e32.

📒 Files selected for processing (2)
  • .github/workflows/release-bump-version.yml
  • libs/cua-driver/.bumpversion.cfg

📝 Walkthrough

Walkthrough

This pull request integrates version bumping support for a new cua-driver library into the CI/CD pipeline. It adds workflow configuration to accept cua-driver as a bump target, automatically updates the Swift version constant, and emits the bumped version for downstream publishing workflows.

Changes

Cohort / File(s) Summary
cua-driver version bumping integration
.github/workflows/release-bump-version.yml, libs/cua-driver/.bumpversion.cfg
Workflow now accepts cua-driver as a bump target and maps it to libs/cua-driver directory. New bumpversion config specifies version starting at 0.0.1 and defines rules to update CuaDriverCore.swift with public static let version constant. Post-bump step parses the updated version and emits it as standard output for downstream tag creation/publishing flows.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A driver seeks its version true,
In Swift we write the bumps anew,
From workflow's hand to config's care,
The rabbit hops version bumps everywhere! 🚀

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and accurately describes the main change: integrating cua-driver into the release-bump-version CI workflow.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch wire-cua-driver-bump

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant