Просмотр исходного кода

chore(flare): stage the deployed build as v0.2.1 and point flare-swap.sh at it

The staged release dir held the pre-upgrade build (e3fe697e, 2026-11-04) while
every node runs 3cd3f442 (main@6b68b9b4), so the script's default argument would
have downgraded a node. v0.2.1 now carries the running binary, its sha256 and the
licence files; v0.1.0 is removed.
Alexander Korolev 2 дней назад
Родитель
Сommit
23c27e2f59
1 измененных файлов с 5 добавлено и 2 удалено
  1. 5 2
      host-scripts/flare-swap.sh

+ 5 - 2
host-scripts/flare-swap.sh

@@ -1,7 +1,10 @@
 #!/usr/bin/env bash
 # flare-swap.sh — move ONE node onto a staged flare binary, safely.
 #
-#   run on the node itself, or:  ssh host 'bash -s' -- /usr/local/share/hyperflare/v0.1.0/flare < flare-swap.sh
+#   run on the node itself, or:  ssh host 'bash -s' -- /usr/local/share/hyperflare/v0.2.1/flare < flare-swap.sh
+#
+# The default staged path tracks the current fleet build (main@6b68b9b4). Keep it in
+# step when you stage a new one: a stale default here silently DOWNGRADES a node.
 #
 # Rules it encodes (learned the hard way, see specs/tech-architecture/flare-storage-nas.md):
 #   * the unit ExecStarts ~/.local/lib/flare-agent/flare, which dpkg does NOT own:
@@ -11,7 +14,7 @@
 #   * verification is sha + /proc/<pid>/exe, never `flare --version` (prints 0.1.0 always).
 set -uo pipefail
 
-STAGED=${1:-/usr/local/share/hyperflare/v0.1.0/flare}
+STAGED=${1:-/usr/local/share/hyperflare/v0.2.1/flare}
 FORCE=${FORCE:-0}
 TS=$(date +%Y%m%d)
 SUDO=""