Skip to content

docs: fix stale version-bump-check description in AGENTS.md #98

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
baxyz merged 1 commit into from
Sep 9, 2026
Merged

docs: fix stale version-bump-check description in AGENTS.md #98

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/<name>/README.md` changed under `src/<name>/` or
`test/<name>/`. It's a blocking check only — it never commits a bump on your
behalf (deliberately:
other than `src/<name>/README.md` changed under `src/<name>/`, or
`test/<name>/test.sh` specifically changed (a new `test/<name>/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.
Expand Down
Loading