agent-ops
OPS-179
· child of OPS-173 gitpush.sh split by stack: retire the 2408-line monolith, per-stack scripts, bump-after-gate, deploy health poll Backlog
gitpushnextjs.sh
Done normal
bvbin-venus-cc
Next.js is the only stack where the bump target is deterministic (package.json, resolved via .sitebump PKG_PATH when the app is not at the repo root). Carry over from gitpush.sh: the cap+rollup MAJOR.MINOR.PATCH bump, the resolved-path staging (staging a literal package.json in an app-subdir repo stages nothing and silently drops the bump), and the .gitpush-pre.sh gate MINUS the production build - Vercel builds on deploy and a local Turbopack build is unbounded work that contributed to a venus OOM cascade on 2026-08-09. Sources gitpush-core.sh (OPS-174); bump order per OPS-175. New script, explicitly NOT backwards compatible with gitpush.sh - no flag aliasing, no compatibility shims.
Activity
-
parent=#3117
-
MEASURED 2026-10-05 (bin-venus-cc): gitpushnextjs.sh exists at VERSION=1.1, 16897 bytes, executable. Bump-after-gate built in from v1.0 (:27). Required bump flag with a real abort on absence, deliberately unlike gitpush.sh's old banner-then-bump-anyway (replaced in 7cf82ee's diff to this file, which states the OPS-187 red banner 'is gone with it'). Next.js detection is the redesigned, defect-free form: gpn_pkg_path() reads PKG_PATH= from .sitebump and defaults to package.json, then greps a quoted "$PKG" for '"next"' and REFUSES rather than falling back (:114-140). That redesign is what closed the third site of OPS-130 - the old 'git ls-files "*package.json"' glob piped into grep is gone entirely.
-
Done: gitpushnextjs.sh v1.1 live, and its PKG_PATH redesign also retired one of OPS-130's three quoted-path sites.
task
6w ago by wi-cli-venus
1w ago
2026-10-05 17:50