Skip to content

ci: register conductor in create-tag + release workflows - #61

Merged
rohitg00 merged 1 commit into
mainfrom
chore/release-conductor
Apr 29, 2026
Merged

ci: register conductor in create-tag + release workflows#61
rohitg00 merged 1 commit into
mainfrom
chore/release-conductor

Conversation

@rohitg00

@rohitg00 rohitg00 commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #59 (conductor worker merged). Register conductor with the two workflows that hardcode the worker list:

  • `.github/workflows/create-tag.yml` — adds `conductor` to the `worker` input choice list so `gh workflow run create-tag.yml -f worker=conductor -f bump=patch -f tag=latest` is dispatchable from the Actions UI.
  • `.github/workflows/release.yml` — adds `conductor/v*` to the tag-push trigger so a tag pushed by Create Tag fires the release dispatcher (multi-arch binaries + GH Release + `POST /publish`).

Both lists kept alphabetical between `coding` and `eval`.

After merge

  1. Actions → Create Tag → `worker: conductor, bump: patch, tag: latest` → run.
  2. Workflow tags `conductor/v0.1.1` and pushes — release dispatcher runs.
  3. Multi-arch `iii-conductor` binaries land in the GitHub Release for that tag.
  4. `POST https://api.workers.iii.dev/publish\` registers conductor for `iii worker add conductor`.

(The version bumps from 0.1.0 → 0.1.1 because Create Tag always increments. Initial register is fine at 0.1.1.)

Test plan

  • CI passes (no worker changes in this PR; only workflow YAML)
  • After merge, dispatch Create Tag and confirm tag appears
  • Confirm release.yml runs to completion against `conductor/v0.1.1`

Summary by CodeRabbit

  • Chores
    • Enabled automated release process for the conductor module.

Adds the conductor worker (merged in #59) to the Create Tag workflow's
choice list and to the Release workflow's tag-push trigger so
`gh workflow run create-tag.yml -f worker=conductor` works and
`conductor/v*` tags fire the release dispatcher.

Both lists kept alphabetical between coding and eval.
@coderabbitai

coderabbitai Bot commented Apr 29, 2026

Copy link
Copy Markdown

Caution

Review failed

Pull request was closed or merged during review

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: 6f8c08ef-dc15-4eb8-a93d-8017747e60bd

📥 Commits

Reviewing files that changed from the base of the PR and between e83cc71 and 8dfe018.

📒 Files selected for processing (2)
  • .github/workflows/create-tag.yml
  • .github/workflows/release.yml

📝 Walkthrough

Walkthrough

GitHub Actions workflow configurations updated to include the conductor module in tag creation and release triggers. The create-tag workflow now allows manual selection of conductor for version bumping, and the release workflow triggers on conductor version tag pushes.

Changes

Cohort / File(s) Summary
Workflow Dispatch Configuration
.github/workflows/create-tag.yml
Added conductor as a selectable option in the worker input for manual workflow dispatch, enabling tag/version bumping for the conductor module.
Release Trigger Configuration
.github/workflows/release.yml
Added conductor/v* tag pattern to the push trigger, enabling the release workflow to execute when conductor version tags are pushed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops with glee, so bright, ✨
The conductor now joins the tag and release flight!
With workflows aligned in perfect harmony,
Our modules march forward—wild and free! 🐰🚂

🚥 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 accurately describes the main change: registering the conductor module in two CI workflows (create-tag and release). It is concise, specific, and reflects the core objective of the changeset.
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 chore/release-conductor

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
Review rate limit: 0/1 reviews remaining, refill in 60 minutes.

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