Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

Gate VMs install a current git from the git-core PPA

garrytand45a98df034f
diff --git a/CHANGELOG.md b/CHANGELOG.md
index b6b7959adf..781d70278b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,18 @@ credits are retained; no result has been reassigned to another provider. Origina
identifiers and attribution are available in the pre-removal Git revision
`6040075c6cb95be5881cc2e1b76ef7d71f4e5d29` (retained on 2026-09-23).
+## [Unreleased]
+
+### The Ubicloud gate VMs run a current git
+
+**The test suite passes on a gate VM again.** Gate VMs ran stock Ubuntu 24.04's git 2.43. GitHub's runners and dev machines are on 2.5x. Three test files depend on newer git:
+- `test/effect-git-secret-gate.test.ts` needs `git maintenance run --detach`, which arrived in git 2.47.
+- `test/sync-partial-clone-2331.test.ts` (both the unit and PostgreSQL arms) needs newer partial-clone behaviour.
+
+Because of that, every VM gate (`bun run ci:ubicloud`, `scripts/pregate-remote-gate.sh` when it can't reuse a CI run) failed those files no matter what the change was.
+
+- `scripts/ubicloud/setup-ci-vm.sh` now installs git from the git-core PPA, as GitHub's runner images do. It requires at least git 2.47.0 (`GIT_MIN`) and fails setup with the version it found when git is older. A prebuilt image whose git is older than that no longer counts as ready, so it runs the apt step too. On one standard-16 VM, setup took 97 s and installed git 2.56.1. All three files passed there: effect-git-secret-gate 29/0, sync-partial-clone-2331 unit 12/0, its PostgreSQL arm 23/0. sync-disabled-cycle-window's PostgreSQL arm also passed, 7/0.
+
## [0.60.691.0] - 2026-11-12
**A privacy label repair on a database-only page now sticks, and a supported command stops tracking a folder's files without deleting their pages.** Pages under a folder declared `storage.db_only` in `gbrain.yml` live in the database. Some of those folders still had files Git tracked from before the declaration, and on a git-canonical source every sync put the committed file back over the database, undoing a `gbrain repair visibility` that had made the page private. Sync now keeps the database version there, a commit to such a file can no longer widen who reads the page, and `gbrain git commit-push --untrack` takes the old files out of Git safely so the problem cannot come back.
diff --git a/scripts/ubicloud/setup-ci-vm.sh b/scripts/ubicloud/setup-ci-vm.sh
index 85aebfdda8..5c9df61272 100755
--- a/scripts/ubicloud/setup-ci-vm.sh
+++ b/scripts/ubicloud/setup-ci-vm.sh
@@ -8,7 +8,10 @@
# - node (pinned; NODE_VERSION, matching native-locks.yml's setup-node, from
# nodejs.org and checksum-verified: apt's Node 18 cannot import a .ts file,
# which test/skill-resolver-packaging.test.ts does)
-# - git, python3, procps, psql, jq, cc, timeout (test prerequisites)
+# - git, python3, procps, psql, jq, cc, timeout (test prerequisites); git
+# comes from the git-core PPA, as on GitHub's runners, because stock
+# Ubuntu 24.04 ships 2.43 and the suite needs GIT_MIN (maintenance
+# run --detach, partial-clone lazy-fetch behaviour)
# - SLOTS isolated pgvector/pgvector:pg16 servers, each fronted by a
# transaction-mode PgBouncer, so every E2E slot owns its whole server just
# as each ci:local shard owns postgres-N (slot i: postgres on
@@ -44,6 +47,8 @@ CHECKOUT="${CHECKOUT:-.}"
CHECKOUT_MARKER="${CHECKOUT_MARKER:-}"
GITLEAKS_VERSION=8.30.1
APT_PACKAGES=(git ca-certificates python3 procps postgresql-client jq gcc libc6-dev)
+GIT_PPA=ppa:git-core/ppa
+GIT_MIN=2.47.0
PG_IMAGE="${PG_IMAGE:-pgvector/pgvector:pg16}"
PGBOUNCER_IMAGE=edoburu/pgbouncer:latest
# Throwaway password of the loopback-only test servers (docker-compose.ci.yml uses the same).
@@ -71,6 +76,12 @@ apt_get() {
-o Acquire::IndexTargets::deb::CNF::DefaultEnabled=false "$@" >/dev/null
}
+git_current() {
+ local have
+ have=$(git --version 2>/dev/null | awk '{print $3}')
+ [ -n "$have" ] && [ "$(printf '%s\n' "$GIT_MIN" "$have" | sort -V | head -1)" = "$GIT_MIN" ]
+}
+
# Docker first so the image pulls overlap the rest of apt. Containers start
# only once apt is done: a package's systemd reload while Docker creates a
# container's scope unit fails the `docker run` ("Message recipient
@@ -78,11 +89,17 @@ apt_get() {
install_system() {
local pg_pull pgb_pull bin baked=1
for bin in docker psql cc jq git; do command -v "$bin" >/dev/null || baked=0; done
+ git_current || baked=0
if [ "$baked" = 1 ]; then
sudo docker pull -q "$PG_IMAGE" >/dev/null
sudo docker pull -q "$PGBOUNCER_IMAGE" >/dev/null
return
fi
+ command -v add-apt-repository >/dev/null || {
+ apt_get update
+ apt_get install -y --no-install-recommends software-properties-common
+ }
+ sudo add-apt-repository -y -n "$GIT_PPA" >/dev/null
apt_get update
apt_get install -y --no-install-recommends docker.io
sudo docker pull -q "$PG_IMAGE" >/dev/null &
@@ -92,6 +109,7 @@ install_system() {
apt_get install -y --no-install-recommends "${APT_PACKAGES[@]}"
wait "$pg_pull"
wait "$pgb_pull"
+ git_current || fail "$(git --version) is older than git $GIT_MIN after installing from $GIT_PPA"
}
if [ "${PREPARE_IMAGE:-0}" = "1" ]; then