From 54569b2c8580215fccc0a7ae62a6ebfbe8eb6faf Mon Sep 17 00:00:00 2001 From: Ansho Rei Date: Thu, 20 Aug 2026 14:54:43 +0200 Subject: [PATCH] Require a version bump decision before every commit Records the rule in the Git Workflow section: decide whether a change warrants a bump, ask before making one, no bump for docs, tests or fixups, and bump once on the final commit when work spans several. Docs only, so no bump for this one. Co-Authored-By: Claude Opus 5 (1M context) --- AGENTS.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index b4d57b8..58002e9 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -60,3 +60,12 @@ - Commit format: `([ticketID]) [short description]` - Use `--fixup` for incremental changes - Test before moving to reviewing status + +### Version Bumps +- Before every commit, decide whether the change warrants a version bump in `Cargo.toml` +- Always ask the user to confirm the bump and its kind before making it — never bump silently, and never skip the question because the answer looks obvious +- Pre-1.0, so: patch for fixes and internal changes, minor for a new command, flag or changed output, major only for a deliberate 1.0 +- No bump for docs-only, tests-only or `--fixup` commits +- When one body of work spans several commits, bump once on the final commit rather than on each +- Bump `Cargo.toml` and the `worklane` entry in `Cargo.lock` together, in the commit that carries the bump +- `worklane --version` reports the crate version alongside the build sha, so the bump is what makes one release distinguishable from another