Tags give the ability to mark specific points in history as being important
-
v0.1.0-alpha.28
protectedb6492dd0 · ·v0.1.0-alpha.28 — BUGS #1516 (recovery-points reads the refused / not-configured / unavailable notices; --from/--until checked locally) + drop monitor from the platform-component map
-
v0.1.0-alpha.27
protected7eb50af8 · ·v0.1.0-alpha.27 — FEATURES #403 (test-email without curl: client probe + relay confirmation)
-
v0.1.0-alpha.26
protected20c631dc · ·v0.1.0-alpha.26 — FEATURES #439 Phase 2b (hook provision/reconcile, rotate --local-only)
-
v0.1.0-alpha.25
protecteda49c9c4d · ·v0.1.0-alpha.25 — FEATURES #442: mecca repo (the AppMecca git host from the CLI)
-
v0.1.0-alpha.24
protectedb08516f6 · ·v0.1.0-alpha.24 — FEATURES #439 Phase 3a: mecca app auto-deploy
-
v0.1.0-alpha.17
protecteddccca2c2 · ·v0.1.0-alpha.17 — exec cancel exit code, test-email hardening
-
v0.1.0-alpha.15
protected42c8c3cb · ·v0.1.0-alpha.15 — mecca access (FEATURES #387 Wave C) + FEATURES #366 C9/H1
-
v0.1.0-alpha.13
protected29875ae3 · ·v0.1.0-alpha.13 — FEATURES #366 P3: app list names each row's group
-
v0.1.0-alpha.11
protected3dd6dd07 · ·0.1.0-alpha.11 — #1230 records renderer + near-miss hint; #1218 route fixes
-
v0.1.0-alpha.10
protecteda296bf03 · ·v0.1.0-alpha.10 — the three fixes alpha.9 could not carry, plus the gate that would have caught it alpha.9 was tagged one commit too early: its tree fails hintResolve on the `mecca app versions` hint (#885's refusal naming a command this CLI lacks), so its publish job failed and nobody saw it. This release carries that fix and the two behind it, and adds the check that makes the next miss loud. #885 the cancel refusal no longer names a command this CLI lacks #1110 `mecca configure` works with no TTY, and its refusal names a real flag #1112 `mecca status` renders the real application table #1111 tags-vs-npm comparison, superseded tags declared with reasons 928 tests green.