ZDDC/zddc/internal/apps/embedded/versions.txt at 76e1e78c55d322bede883caa402268f1329d5e5e - VARASYS/ZDDC - Forgejo: Beyond coding. We forge.

VARASYS/ZDDC

ZDDC 76e1e78c55 chore: ./build is dev-only; ./build alpha is the explicit deploy

Reverts the prior CLI simplification. ./build (no arg) now does source
work only — tool dist/ + cross-compiled zddc-server binaries — and
leaves the website worktree alone. Channel/release cuts are explicit:

  ./build                  dev build (source only, no deploy)
  ./build alpha            cut alpha          (cascades nothing)
  ./build beta             cut beta           (cascades alpha → beta)
  ./build release [X.Y.Z]  cut stable         (cascades all)

Rationale: editing source shouldn't have a side-effect on the live
site. The website worktree at ~/src/zddc-website/ is what Caddy serves
in real time, so any write to it is a deploy. Treating dev iteration
as alpha-publish was confusing — the user wanted source builds and
deploys to be distinct verbs.

Mechanically: a `dev` (default) branch is added to the case statement;
the post-build matrix-index regen + channel-link verifier are
conditional on RELEASE_CHANNEL being set; dev builds skip them.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-02 08:29:58 -05:00

6 lines

311 B

Text

Raw Blame History

 # Generated by build.sh — do not edit. One <app>=<build label> per line.
 archive=v0.0.9-alpha · 2026-05-02 · 6167e99
 transmittal=v0.0.9-alpha · 2026-05-02 · 6167e99
 classifier=v0.0.9-alpha · 2026-05-02 · 6167e99
 mdedit=v0.0.9-alpha · 2026-05-02 · 6167e99
 landing=v0.0.9-alpha · 2026-05-02 · 6167e99