ci(release): allow tagging on development or main #57

Merged

mik-tf merged 1 commit from development_mik_release_gate into development

2026-05-03 16:56:08 +00:00

mik-tf commented

2026-05-03 16:55:26 +00:00

Owner

Mirrors hero_proxy's release.yaml gate, which accepts tags reachable from development or main (vs. main-only here).

What

Two-line edit on .forgejo/workflows/release.yaml's Verify tag is on ... step:

-      - name: Verify tag is on main branch
+      - name: Verify tag is on development or main
         run: |
-          git fetch origin main
+          git fetch origin development main
-          if ! git branch -r --contains "$TAG_COMMIT" | grep -qE 'origin/main'; then
+          if ! git branch -r --contains "$TAG_COMMIT" | grep -qE 'origin/(development|main)'; then

No other steps change — build (cargo build --workspace --release) and upload-to-Forgejo-release behaviour are byte-identical.

Why

The --from-ci rollout for the wider Hero stack (hero_demo#54) needs a fresh hero_aibroker release that includes hero_aibroker_services (renamed in commit 591e071, after v0.1.0 / 2026-04-02). The current main-only gate would force a development → main merge before any new tag can publish, which is more ceremony than the rest of the working repos in the stack require.

Test plan

Squash-merge to development
Push v0.1.1 tag at the new development HEAD
Confirm release.yaml workflow run passes the gate and uploads hero_aibroker{,_server,_ui,_services}-linux-amd64-musl assets to the v0.1.1 Forgejo release
Run service_aibroker install --from-ci on heroci.gent01.grid.tf and confirm all 4 binaries land in ~/hero/bin/

Signed-off-by: mik-tf

Mirrors [hero_proxy's release.yaml](https://forge.ourworld.tf/lhumina_code/hero_proxy/src/branch/development/.forgejo/workflows/release.yaml#L36-L45) gate, which accepts tags reachable from `development` or `main` (vs. main-only here). ## What Two-line edit on `.forgejo/workflows/release.yaml`'s `Verify tag is on ...` step: ```diff - - name: Verify tag is on main branch + - name: Verify tag is on development or main run: | - git fetch origin main + git fetch origin development main - if ! git branch -r --contains "$TAG_COMMIT" | grep -qE 'origin/main'; then + if ! git branch -r --contains "$TAG_COMMIT" | grep -qE 'origin/(development|main)'; then ``` No other steps change — build (`cargo build --workspace --release`) and upload-to-Forgejo-release behaviour are byte-identical. ## Why The `--from-ci` rollout for the wider Hero stack ([hero_demo#54](https://forge.ourworld.tf/lhumina_code/hero_demo/issues/54)) needs a fresh hero_aibroker release that includes `hero_aibroker_services` (renamed in commit 591e071, after v0.1.0 / 2026-04-02). The current main-only gate would force a development → main merge before any new tag can publish, which is more ceremony than the rest of the working repos in the stack require. ## Test plan - [ ] Squash-merge to development - [ ] Push `v0.1.1` tag at the new development HEAD - [ ] Confirm `release.yaml` workflow run passes the gate and uploads `hero_aibroker{,_server,_ui,_services}-linux-amd64-musl` assets to the v0.1.1 Forgejo release - [ ] Run `service_aibroker install --from-ci` on heroci.gent01.grid.tf and confirm all 4 binaries land in `~/hero/bin/` Signed-off-by: mik-tf

mik-tf added 1 commit

2026-05-03 16:55:26 +00:00

ci(release): allow tagging on development or main, mirror hero_proxy gate

Build and Test / build-and-test (pull_request) Failing after 2m5s

Details

10ee8b4aae

The "Verify tag is on main branch" step required the tag commit to be
reachable from origin/main, which forces every release to first land a
development → main merge. hero_proxy's release.yaml uses a more permissive
gate that accepts either branch — adopt it here so we can cut release
tags directly off development without a separate main-merge ceremony.

Diff is the gate step's name + check: replaces the main-only branch
match with a (development|main) regex, mirroring hero_proxy line-for-line.
No other release.yaml steps change; build + upload behaviour is identical.

Needed for the --from-ci rollout
(lhumina_code/hero_demo#54): the latest
release v0.1.0 (2026-04-02) predates hero_aibroker_services, so
service_aibroker install --from-ci would 404. A fresh tag on the current
development tip will publish the four binaries the consumer expects.

Signed-off-by: mik-tf