AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).
docs(release): document forcing a version with Release-As (#210)
Rufuse71a025af7bc
diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.ymlindex ec298350..b7f5e717 100644--- a/.github/workflows/release-please.yml+++ b/.github/workflows/release-please.yml@@ -10,6 +10,13 @@# Merges that are only chore/docs/test/refactor do not start a release on# their own; they ride along with the next feat or fix.#+# To pick a bigger version without calling anything breaking, end a PR+# description with a `Release-As: X.Y.Z` line; it lands on main as a commit+# footer and sets the next release only. To correct a merged PR's message+# (e.g. drop a wrong `!`), add a BEGIN_COMMIT_OVERRIDE / END_COMMIT_OVERRIDE+# block holding the corrected message to that PR's description; it is read+# on the next push to main.+## Merging the release PR makes this workflow tag the merge commit `vX.Y.Z`# and create the GitHub Release from the changelog entry. The tag push then# runs release-images.yml, which publishes the images (its own release jobdiff --git a/CLAUDE.md b/CLAUDE.mdindex 07769da5..5ab9912a 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -224,6 +224,14 @@ cd evals && python run_evals.py --scenarios scenarios/ --output results/change is, not by how big it is. PRs are squash-merged with the PR title asthe commit subject, which is what release-please reads — branch commitmessages do not reach `main`.+- `!` / `BREAKING CHANGE:` only for a real break (a removed or reshaped+ endpoint, a new required env var, a migration an operator must run) — never+ to get a bigger bump. To release a larger version for any other reason, end+ one PR's description with a `Release-As: X.Y.Z` line (the squash body is the+ PR body, so it lands on `main` as a footer). It applies to the next release+ only. To un-mark a merged PR, add a `BEGIN_COMMIT_OVERRIDE` /+ `END_COMMIT_OVERRIDE` block with the corrected message to its description;+ release-please picks it up on the next push to `main`.- PR description is three sections and nothing else: **Problem**, **Approach**,**Checklist** (see `.github/PULL_REQUEST_TEMPLATE.md`). Rationale, reviewfindings and alternatives go in the commit message; open questions go in the