ci(lab-publish): derive release tag from branch (development→latest-dev) #38

Merged
fatmaebrahim merged 1 commit from ci_release_tag_main into main 2026-06-09 12:45:14 +00:00
Member

The lab-publish workflow was uploading binaries to the same latest release tag regardless of which branch triggered it, causing development builds to overwrite stable binaries and vice versa.
This adds a branch-to-tag mapping (main→latest, development→latest-dev, v* tags keep their name) and passes --release-tag to lab build so each channel publishes to its own release.
Also triggers the workflow on both branches so the logic is active everywhere.

The `lab-publish` workflow was uploading binaries to the same `latest` release tag regardless of which branch triggered it, causing development builds to overwrite stable binaries and vice versa. This adds a branch-to-tag mapping (main→`latest`, development→`latest-dev`, v* tags keep their name) and passes --release-tag to lab build so each channel publishes to its own release. Also triggers the workflow on both branches so the logic is active everywhere.
ci(lab-publish): derive release tag from branch (development→latest-dev)
All checks were successful
Build and Test / build (pull_request) Successful in 17m36s
5a6fa6fedb
fatmaebrahim deleted branch ci_release_tag_main 2026-06-09 12:45:14 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_browser!38
No description provided.