From d1a50cc95a114cae24499f1ca07143849d77d86a Mon Sep 17 00:00:00 2001 From: baxyz Date: Wed, 9 Sep 2026 19:41:48 +0000 Subject: [PATCH] =?UTF-8?q?docs(CI-CD):=20=F0=9F=93=9D=20fix=20stale=20ver?= =?UTF-8?q?sion-bump-check=20description?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Found during a final consistency audit after #97: this paragraph still described the pre-fix, broader behavior (any file under test// triggers a bump) instead of the corrected one (test//test.sh specifically — a scenario file doesn't count). Co-Authored-By: Claude Sonnet 5 --- AGENTS.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 976a8f1..10444a8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -111,9 +111,10 @@ reaches the published site. Judgment call, not enforced either way. Enforced by the `version-bump-check` job in `pr-validation.yml`: it fails the PR if a touched feature's `version` is unchanged from `main` *and* something -other than `src//README.md` changed under `src//` or -`test//`. It's a blocking check only — it never commits a bump on your -behalf (deliberately: +other than `src//README.md` changed under `src//`, or +`test//test.sh` specifically changed (a new `test//scenarios.json` +or scenario script doesn't count — see "Testing non-default options" above). +It's a blocking check only — it never commits a bump on your behalf (deliberately: no bot commits, no push-permission/fork edge cases, consistent with how `conventional-commits` already works in this repo). Bump the version yourself and push again.