@rtorcato/repo-tooling 3.9.0 → 3.9.1

package/AGENTS.md

@@ -100,7 +100,7 @@ npx @rtorcato/repo-tooling fix bun --yes --json         # Bun runtime/test confi
 
 ## Conventions in this repo
 
-- Conventional commits enforced via commitlint; header max 72 chars
+- Conventional commits enforced via commitlint; header max 100 chars, body/footer line length unenforced
 - Biome for lint + format (run via `pnpm exec biome check --config-path=tooling/biome/biome.json src scripts`)
 - Tests live alongside source in `tests/`; vitest with no separate config
 - semantic-release runs on push to `main`; `fix:` → patch, `feat:` → minor, `chore:` / `docs:` → no release

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@rtorcato/repo-tooling",
-	"version": "3.9.0",
+	"version": "3.9.1",
 	"description": "One CLI to scaffold, audit and fix your repo's whole toolchain — linting, tests, commits, releases & CI.",
 	"type": "module",
 	"keywords": [

package/tooling/commitlint/commitlint.mjs

@@ -2,11 +2,10 @@ export default {
 	extends: ["@commitlint/config-conventional"],
 	ignores: [
 		(commit) => commit.includes("[skip ci]"),
-		// Bot commit bodies are machine-written blocks (dependabot's
-		// `- dependency-name: …` YAML) that never wrap at 72, so every bot PR
-		// failed body-max-line-length. commitlint can't relax a single rule per
-		// commit, so skip bot commits wholesale — squash-merge uses the PR
-		// title, which is still linted on the merge commit.
+		// Bot commits are machine-written end to end, including headers long
+		// enough to trip header-max-length. Skipping them wholesale keeps bot
+		// PRs green — squash-merge uses the PR title, which is still linted on
+		// the merge commit.
 		// ponytail: matches the trailer, not a bare "[bot]", so a human commit
 		// that merely mentions a bot is still linted.
 		(commit) => /^Signed-off-by: .*\[bot\]/m.test(commit),
@@ -32,10 +31,15 @@ export default {
 		],
 		// 100 is the conventional-commits/semantic-release default. 72 was too
 		// tight: GitHub appends " (#NN)" to squash commits, overflowing the
-		// header on main and skipping the release. Body/footer stay at 72.
+		// header on main and skipping the release.
 		"header-max-length": [2, "always", 100],
-		"body-max-line-length": [2, "always", 72],
-		"footer-max-line-length": [2, "always", 72],
+		// Body/footer length is unenforced. Machine-written commits (agents,
+		// bots) don't wrap, and a `BREAKING CHANGE:` footer — the input
+		// semantic-release reads to cut a major — is the worst thing to make
+		// someone hand-rewrap. The subject rules below decide the release
+		// type and stay enforced.
+		"body-max-line-length": [0],
+		"footer-max-line-length": [0],
 		// Enforce case rules (allow common patterns)
 		"subject-case": [0], // Disable case enforcement to allow flexibility
 		"type-case": [2, "always", "lower-case"],