AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).
chore(ci): bump the patch version for features before 1.0 (#184)
Rufus9adf0372ac30
diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.ymlindex 287f8c6b..ec298350 100644--- a/.github/workflows/release-please.yml+++ b/.github/workflows/release-please.yml@@ -2,8 +2,9 @@## Every push to main runs release-please. PRs are squash-merged with the PR# title as the commit subject, so it reads the PR titles merged since the-# last release (`feat` → minor, `fix` → patch; before-# 1.0 a breaking change is also a minor) and opens or updates one PR titled+# last release (before 1.0: `feat` and `fix` → patch, a breaking change →+# minor; from 1.0: `feat` → minor, `fix` → patch, breaking → major) and opens+# or updates one PR titled# "chore(main): release X.Y.Z". That PR bumps every place the version is# written (see release-please-config.json) and adds the CHANGELOG.md entry.# Merges that are only chore/docs/test/refactor do not start a release ondiff --git a/CLAUDE.md b/CLAUDE.mdindex 0ca5abce..d9bc280b 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -217,8 +217,9 @@ cd evals && python run_evals.py --scenarios scenarios/ --output results/`ui`, `deps`, …), not a file path; drop it only when the change genuinelyspans the repo. Say what changed rather than what it is about, lowercaseafter the colon, no trailing period. See `.github/PULL_REQUEST_TEMPLATE.md`.- The type sets the next version (release-please: `feat` → minor, `fix` →- patch; `chore`/`docs`/`test`/`refactor` release nothing on their own), and+ The type sets the next version (release-please, before 1.0: `feat` and `fix`+ → patch, a breaking change (`!` / `BREAKING CHANGE:`) → minor;+ `chore`/`docs`/`test`/`refactor` release nothing on their own), and`feat`/`fix` titles become the changelog lines, so pick the type by what thechange 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 commitdiff --git a/docs/deployment.md b/docs/deployment.mdindex f79b930d..046f49a4 100644--- a/docs/deployment.md+++ b/docs/deployment.md@@ -65,8 +65,11 @@ thing that builds `Dockerfile.ui`.runs release-please on every push to `main` and keeps one open PR,"chore(main): release X.Y.Z", up to date. PRs are squash-merged, so each onelands as a single commit whose subject is the PR title, and the version comes-from those titles' conventional-commit types since the last release: `feat` → minor,-`fix` → patch, and before 1.0 a breaking change is also a minor. The PR bumps+from those titles' conventional-commit types since the last release. Before 1.0,+`feat` and `fix` both bump the patch version and a breaking change (`!` or a+`BREAKING CHANGE:` footer) bumps the minor; minor versions are kept for+milestones. From 1.0 the usual rule applies: `feat` → minor, `fix` → patch,+breaking → major. The PR bumpsevery place the version is written (listed in `release-please-config.json`)and adds the `CHANGELOG.md` entry, which can be edited in the PR beforemerging. Merges that are only `chore`/`docs`/`test`/`refactor` wait for thediff --git a/release-please-config.json b/release-please-config.jsonindex 79dc8f30..55448f8c 100644--- a/release-please-config.json+++ b/release-please-config.json@@ -9,7 +9,7 @@"package-name": "openexecutive","changelog-path": "CHANGELOG.md","bump-minor-pre-major": true,- "bump-patch-for-minor-pre-major": false,+ "bump-patch-for-minor-pre-major": true,"changelog-sections": [{ "type": "feat", "section": "Added" },{ "type": "fix", "section": "Fixed" },