From 3fe318f4bc15013f694fca39fa999cfdfa60434b Mon Sep 17 00:00:00 2001 From: Ali Ibrahim Jr <48456829+IBJunior@users.noreply.github.com> Date: Fri, 23 Oct 2026 13:00:35 +0200 Subject: [PATCH] docs(readme): point new clones at v4 Co-Authored-By: Claude Opus 5.5 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 66ae9b7..b96e53e 100644 --- a/README.md +++ b/README.md @@ -109,7 +109,7 @@ You pick the provider and model **in the app**, not in the environment — with Cameron says it's unconfigured rather than guessing. `.env` only ever holds the keys. ```bash -git clone --branch v3 https://github.com/agentailor/cameron +git clone --branch v4 https://github.com/agentailor/cameron cd cameron cp .env.example .env # add your model API key, if your provider needs one @@ -119,7 +119,7 @@ docker compose --profile full up # http://localhost:3100 That builds the app, waits for Postgres, applies migrations, and starts everything. Nothing but Docker is needed on your machine. -> **Why `--branch v3`?** Tags are the stable points — each one matches a published article and has +> **Why `--branch v4`?** Tags are the stable points — each one matches a published article and has > passed CI before release. `main` is the working trunk and runs ahead of the latest tag between > articles, so it may carry half-finished work. Clone the [latest > release](https://github.com/agentailor/cameron/releases/latest) to start from something known