ci(lab-publish): derive release tag from branch (development→latest-dev) #38
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_browser!38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci_release_tag_main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
lab-publishworkflow was uploading binaries to the samelatestrelease 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.