lhumina_code/hero_planner
0
0
Fork 0
Code Issues 3 Pull requests Projects Releases 4 Packages Wiki Activity Actions

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

Merged
sameh-farouk merged 1 commit from development_sameh_ci_release_tag into development 2026-06-07 17:35:44 +00:00
Conversation 0 Commits 1 Files changed 1 +17 -7
sameh-farouk commented 2026-06-07 17:35:24 +00:00
Member
Copy link

Fixes hero_planner's development publish, which uploaded every push to the latest release (no --release-tag; lab defaults to latest), clobbering the stable channel.

Now development pushes publish to latest-dev (lab auto-marks -dev tags as prerelease) via the canonical lab --release-tag approach. Kept this repo's RUST_MIN_STACK guard, Rust 1.95, and inline git-auth.

Scope: development only. main currently runs a separate hand-rolled rolling-release workflow (mik-tf, June 3) that already publishes per-branch (latest / dev). Standardizing main on this canonical approach — and aligning the dev tag to latest-dev — is deferred pending coordination with mik-tf, so main is intentionally untouched here.

Verified: YAML + bash -n pass; tags derive main->latest, development->latest-dev, v0.9.0->v0.9.0.

Fixes hero_planner's `development` publish, which uploaded **every** push to the `latest` release (no `--release-tag`; lab defaults to `latest`), clobbering the stable channel. Now `development` pushes publish to **`latest-dev`** (lab auto-marks `-dev` tags as prerelease) via the canonical `lab --release-tag` approach. Kept this repo's RUST_MIN_STACK guard, Rust 1.95, and inline git-auth. **Scope: `development` only.** `main` currently runs a separate hand-rolled rolling-release workflow (mik-tf, June 3) that already publishes per-branch (`latest` / `dev`). Standardizing `main` on this canonical approach — and aligning the `dev` tag to `latest-dev` — is **deferred pending coordination with mik-tf**, so `main` is intentionally untouched here. Verified: YAML + `bash -n` pass; tags derive `main->latest`, `development->latest-dev`, `v0.9.0->v0.9.0`.
development uploaded every push to the `latest` release (no --release-tag, lab
defaults to `latest`), clobbering the stable `latest` channel. Adopt the
canonical per-branch tag logic via lab:
  - 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". Kept this repo's
local CI specifics (RUST_MIN_STACK SIGSEGV guard, Rust 1.95, inline git-auth for
private hero_web_template dep).

Scope: development only. `main` currently runs a separate hand-rolled
rolling-release workflow (per-branch latest/`dev`); standardizing it on this
canonical approach is deferred pending coordination with its author (mik-tf).
sameh-farouk merged commit eed1352896 into development 2026-06-07 17:35:44 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
area:admin

Admin dashboard (hero_planner_admin)

  
area:backend

Server / RPC / store (hero_planner_server/lib)

  
area:web-ui

End-user web app (hero_planner_web)

  
bug

Something is broken or behaves incorrectly

  
enhancement

Improvement to existing functionality

  
feature-request

A new capability that does not exist yet

  
good-first-issue

Small, self-contained, clear fix

  
ux

Usability / discoverability

No labels
area:admin
area:backend
area:web-ui
bug
enhancement
feature-request
good-first-issue
ux
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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_planner!15
No description provided.