Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

Wire up release-backend alongside release-cli, fix backend's own tag suffix

0xken15a71b143213c8
diff --git a/Makefile b/Makefile
index d73be70f2..042acf33c 100644
--- a/Makefile
+++ b/Makefile
@@ -4,18 +4,25 @@
# make install-cli ARGS="--no-restart"
# make upload-cli ARGS="0.1.0"
-.PHONY: cli-test install-cli upload-cli release remote-machine
+.PHONY: cli-test install-cli upload-cli release-cli release-backend remote-machine
## cli-test: typecheck + run the CLI test suite.
cli-test:
cd cli && npx tsc --noEmit && npx vitest run
-## release: tag this commit and push the tag — CI bundles the CLI, publishes it to GCS, and cuts the
-## GitHub Release. The version is bumped from max(last git tag, live metadata.json's `cli` key).
-## ARGS="--dry-run" to preview.
-release:
+## release-cli: tag this commit vX.Y.Z_cli and push the tag — CI bundles the CLI, publishes it to
+## GCS, and cuts the GitHub Release. The version is bumped from max(last git tag, live
+## metadata.json's `cli` key). The `_cli` suffix is a tag-trigger marker only (see cli/RELEASE.md);
+## it never appears in the published version. ARGS="--dry-run" to preview.
+release-cli:
bash cli/scripts/release-cli.sh $(ARGS)
+## release-backend: tag this commit vX.Y.Z_api and push the tag — CI builds the backend's Docker
+## image and rolls it out. ARGS=minor|major|X.Y.Z to bump differently, ARGS=--dry-run to preview.
+## See backend/scripts/release-be.sh.
+release-backend:
+ bash backend/scripts/release-be.sh $(ARGS)
+
## install-cli: bundle the CLI from THIS working tree and install it into ~/.harness/cli — the local dev
## loop, nothing published. Restarts the daemon on the new bytes. Self-update stays ON: the build is
## labelled with the published version, which the release you are level with cannot outrank, so your bytes
diff --git a/backend/README.md b/backend/README.md
index 65c90771a..93cf1472c 100644
--- a/backend/README.md
+++ b/backend/README.md
@@ -65,12 +65,17 @@ When direct ICE fails, the terminal opens on WebSocket relay automatically.
`../.github/workflows/production-be-build.yaml` builds and pushes the production Docker image on
tag push. Backend releases are tagged **`vX.Y.Z_api`** — the `_api` suffix is what routes the push
to this workflow instead of the CLI's `../.github/workflows/release.yml` (which only reacts to
-`vX.Y.Z_cli`), now that both live in this one repo:
+`vX.Y.Z_cli`), now that both live in this one repo. Cut one with:
```bash
-git tag vX.Y.Z_api && git push origin vX.Y.Z_api
+make release-backend # patch bump
+make release-backend ARGS=minor # or major
+make release-backend ARGS="1.4.1" # exact version
+make release-backend ARGS=--dry-run # preview, tags/pushes nothing
```
+(equivalent to `bash backend/scripts/release-be.sh`, see that script for details).
+
## Persistence
Prisma over the **same MongoDB** as the agent-manager (no migration files — `prisma db push` at
diff --git a/backend/scripts/release-be.sh b/backend/scripts/release-be.sh
index d741efb41..acbb4468b 100755
--- a/backend/scripts/release-be.sh
+++ b/backend/scripts/release-be.sh
@@ -1,16 +1,19 @@
#!/usr/bin/env bash
-# Cut a backend release: bump the version, tag HEAD `vX.Y.Z`, push the tag.
+# Cut a backend release: bump the version, tag HEAD `vX.Y.Z_api`, push the tag.
#
-# ./scripts/release-be.sh # patch bump (v1.1.2 -> v1.1.3)
-# ./scripts/release-be.sh minor # v1.1.2 -> v1.2.0
-# ./scripts/release-be.sh major # v1.1.2 -> v2.0.0
-# ./scripts/release-be.sh 1.4.1 # exact version -> v1.4.1
+# ./scripts/release-be.sh # patch bump (v1.1.2_api -> v1.1.3_api)
+# ./scripts/release-be.sh minor # v1.1.2_api -> v1.2.0_api
+# ./scripts/release-be.sh major # v1.1.2_api -> v2.0.0_api
+# ./scripts/release-be.sh 1.4.1 # exact version -> v1.4.1_api
# ./scripts/release-be.sh --dry-run # print what it WOULD do, touch nothing
#
-# Pushing the tag is the whole point: .github/workflows/production-be-build.yaml triggers on
-# SemVer tags (`vX.Y.Z`) and builds
-# Dockerfile.k8s -> autonomous-code-be.
+# Pushing the tag is the whole point: ../.github/workflows/production-be-build.yaml triggers on
+# `vX.Y.Z_api` tags and builds Dockerfile.k8s -> autonomous-code-be.
# The image ArgoCD deploys is named after this tag, so the tag must point at the commit you want live.
+#
+# The `_api` suffix exists only so this tag never also fires the CLI's release workflow
+# (../.github/workflows/release.yml, which reacts to `vX.Y.Z_cli`) now that both live in one repo.
+# It is stripped below before anything treats it as a version.
# Bash 3.2-compatible (macOS default).
set -euo pipefail
@@ -55,10 +58,11 @@ if ! git merge-base --is-ancestor "$HEAD_SHA" "origin/$BRANCH" 2>/dev/null; then
fi
# --- next version: highest valid SemVer release tag, then bump.
+# Tags are "vX.Y.Z_api" — strip "v" and "_api" so LATEST is a bare X.Y.Z.
# `sort -V` handles numeric ordering while grep drops malformed tags.
-LATEST="$(git tag -l 'v*' \
- | { grep -E '^v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)$' || true; } \
- | sed -E 's/^v//' \
+LATEST="$(git tag -l 'v*_api' \
+ | { grep -E '^v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)_api$' || true; } \
+ | sed -E 's/^v//; s/_api$//' \
| sort -V | tail -1)"
LATEST="${LATEST:-0.0.0}"
@@ -74,7 +78,7 @@ case "$BUMP" in
exact) NEXT="$EXACT" ;;
esac
-TAG="v${NEXT}"
+TAG="v${NEXT}_api"
if git rev-parse -q --verify "refs/tags/$TAG" >/dev/null; then
echo "ERROR tag $TAG already exists. Re-tagging a released version breaks the image<->commit mapping." >&2
@@ -83,7 +87,7 @@ fi
echo " service : $SERVICE"
echo " branch : $BRANCH @ $(git rev-parse --short HEAD) $(git log -1 --format=%s | cut -c1-60)"
-echo " latest : v$LATEST"
+echo " latest : v${LATEST}_api"
echo " new tag : $TAG [$BUMP]"
if [[ "$DRY_RUN" == "1" ]]; then
diff --git a/cli/RELEASE.md b/cli/RELEASE.md
index 03914662b..4ec0c5f6a 100644
--- a/cli/RELEASE.md
+++ b/cli/RELEASE.md
@@ -4,11 +4,16 @@ Running daemons self-update from a public GCS bucket (`src/lib/selfUpdate.ts`).
tag: `.github/workflows/release.yml` bundles the CLI, publishes it to that bucket, and cuts the GitHub
Release. **The tag IS the version — CI never bumps.**
+Tags are `vX.Y.Z_cli`, not plain `vX.Y.Z`: the backend now lives in this same repo under `backend/`
+and releases as `vX.Y.Z_api` (see `../backend/README.md`), so the suffix is what tells each tag-push
+trigger which workflow to run. It's stripped before anything treats it as a version — the published
+version everywhere below (manifest, release title, `ADAPTER_VERSION`) is always a bare `X.Y.Z`.
+
```bash
-make release # bump the patch, tag, push — CI does the rest
-make release ARGS="--dry-run" # print the version it would cut and the notes, do nothing
-make release ARGS="0.2.0" # release an explicit version
-make release ARGS="--notes-file notes.md" # hand-written release notes
+make release-cli # bump the patch, tag, push — CI does the rest
+make release-cli ARGS="--dry-run" # print the version it would cut and the notes, do nothing
+make release-cli ARGS="0.2.0" # release an explicit version
+make release-cli ARGS="--notes-file notes.md" # hand-written release notes
```
Nothing is built locally and no GCS credentials are needed: the only things `cli/scripts/release-cli.sh`
@@ -43,7 +48,7 @@ make upload-cli ARGS="--no-build" # upload the existing dist/ artifact as-is
```
**This creates no git tag.** It bumps from the remote manifest, so the repo stops reflecting what's
-published. Prefer `make release`; if you do publish by hand, cut a `make release` afterwards to bring
+published. Prefer `make release-cli`; if you do publish by hand, cut a `make release-cli` afterwards to bring
the tag back in line.
1. Reads the current version from the live manifest (falling back to `package.json` if the manifest is