ci(lab-publish): derive release tag from branch (main->latest, development->latest-dev) #43

Merged

sameh-farouk merged 1 commit from development_sameh_ci_release_tag into development

2026-06-07 16:57:19 +00:00

sameh-farouk commented

2026-06-07 16:50:45 +00:00

Member

Same fix applied to hero_collab (#76/#77).

The publish workflow uploaded every push to the latest release (no --release-tag, lab defaults to latest), so development builds clobbered the stable latest release and the workflow never triggered on main.

Per-branch tag logic now:

Push	Release tag
`main`	`latest` (stable)
`development`	`latest-dev` (prerelease)
`v*` tag	the ref name

Adds main to triggers and passes --release-tag "$TAG". Kept this branch's Rust 1.95 toolchain.

Note: main here was separately bumped to Rust 1.96 and still has the OLD tag logic, so it needs its own fix (a cherry-pick won't apply cleanly across the toolchain divergence) — follow-up PR to main to come.

Verified: YAML + bash -n pass; tag derivation main->latest, development->latest-dev, v2.0.0->v2.0.0.

Same fix applied to hero_collab (#76/#77). The publish workflow uploaded **every** push to the `latest` release (no `--release-tag`, lab defaults to `latest`), so `development` builds clobbered the stable `latest` release and the workflow never triggered on `main`. Per-branch tag logic now: | Push | Release tag | |---|---| | `main` | `latest` (stable) | | `development` | `latest-dev` (prerelease) | | `v*` tag | the ref name | Adds `main` to triggers and passes `--release-tag "$TAG"`. Kept this branch's Rust 1.95 toolchain. **Note:** `main` here was separately bumped to Rust 1.96 and still has the OLD tag logic, so it needs its own fix (a cherry-pick won't apply cleanly across the toolchain divergence) — follow-up PR to `main` to come. Verified: YAML + `bash -n` pass; tag derivation `main->latest`, `development->latest-dev`, `v2.0.0->v2.0.0`.

sameh-farouk added 1 commit

2026-06-07 16:50:45 +00:00

ci(lab-publish): derive release tag from branch (main->latest, development->latest-dev)

Build & Test / check (pull_request) Failing after 21s

Details

Build & Test / check (push) Failing after 21s

Details

b467c4768f

The publish workflow uploaded every push to the `latest` release because no
--release-tag was passed and lab defaults to `latest`, so development builds
clobbered the stable `latest` release and the workflow never triggered on main.

Adopt the canonical per-branch tag logic:
  - push to main        -> latest      (stable)
  - push to development -> latest-dev  (lab marks any `-dev` tag prerelease)
  - push v* tag         -> the ref name (versioned release)

Add `main` to the push triggers and pass --release-tag "$TAG". Matches the
hero_collab fix; kept this branch's Rust 1.95 toolchain as-is.