← Commit history

ship.sh: PUBLISH_PKG defaults to 1 (the real #66 root cause: every ship was invoked with 0, so no skillpack was published since 2.0.276 while lockstep minted empty rows)

John Lauer ·2d4fd81e30 ·2mo ago ·parent 4aeab38
1 file changed +5−1
tools/ship.sh+5−1
@@ -14,7 +14,11 @@ set -euo pipefail VER="${1:?usage: tools/ship.sh <version> \"<changelog>\" [publish_pkg]}" LOG="${2:?changelog sentence required}"-PUBLISH_PKG="${3:-0}"+# pup-bridge#66 (2026-08-23): this defaulted to 0 AND every ship call passed 0 explicitly, so no ship+# since 2.0.276 published the skillpack while release-lockstep minted an empty version row each+# time: the top row had no tarball and `pkg install` 404'd. Lockstep means BOTH artifacts, every+# ship. Publishing is now the default; pass 0 only for a deliberate runtime-only test cut.+PUBLISH_PKG="${3:-1}" REPO="$(cd "$(dirname "$0")/.." && pwd)" PAGE="adom/pup-bridge" ZIP="adom-bridge-puppeteer-v${VER}.zip"