ci(lab-publish): rename dev release tag dev -> latest-dev on main #16

Merged
sameh-farouk merged 1 commit from development_sameh_main_tagname into main 2026-06-07 17:43:45 +00:00
Member

Surgical name fix on main. The custom rolling-release workflow published development builds to a dev release tag; the rest of the ecosystem uses latest-dev. Renamed for consistency, and derived the prerelease flag from the tag (*-dev -> prerelease=true) so the dev channel is correctly marked prerelease.

mik-tf's rolling-release mechanism is left intact — only the tag name + prerelease flag changed. Standardizing on the canonical lab --release-tag approach stays deferred for coordination.

Verified: bash -n passes; derivation gives main -> latest/prerelease=false, development -> latest-dev/prerelease=true.

Surgical name fix on `main`. The custom rolling-release workflow published `development` builds to a **`dev`** release tag; the rest of the ecosystem uses **`latest-dev`**. Renamed for consistency, and derived the prerelease flag from the tag (`*-dev` -> prerelease=true) so the dev channel is correctly marked prerelease. mik-tf's rolling-release mechanism is left intact — only the tag name + prerelease flag changed. Standardizing on the canonical `lab --release-tag` approach stays deferred for coordination. Verified: `bash -n` passes; derivation gives `main -> latest`/prerelease=false, `development -> latest-dev`/prerelease=true.
main's custom rolling-release workflow published development builds to a `dev`
release tag, diverging from the rest of the ecosystem (hero_collab, hero_livekit,
hero_proc canonical) which use `latest-dev`. Rename it for consistency.

Also derive the prerelease flag from the tag name (`*-dev` -> prerelease=true),
matching lab's behaviour, so the renamed latest-dev release is correctly marked
prerelease while stable `latest` stays a full release.

Surgical name fix only — mik-tf's custom rolling-release mechanism is left
intact; standardizing it on the canonical `lab --release-tag` approach remains
deferred for coordination.
Sign in to join this conversation.
No description provided.