@rheged-studio/commitlint-config 1.0.3 → 2.0.0

package/README.md

@@ -7,7 +7,7 @@ It **single-sources** the estate's allowed [Conventional Commit](https://www.con
 - the reusable CI workflow (`reusable-validate-commits.yml`) that validates a PR's `base..head` commit range, and
 - the local husky `pre-push` hook that runs the same range check before a push ever reaches CI.
 
-It extends [`@commitlint/config-conventional`](https://www.npmjs.com/package/@commitlint/config-conventional) and retains all of its defaults — only the list of allowed commit types is pinned to the estate's set.
+It extends [`@commitlint/config-conventional`](https://www.npmjs.com/package/@commitlint/config-conventional) and pins `type-enum` plus the estate's length rules (`header-max-length` 72, `body-max-line-length` 256, `footer-max-line-length` 256). Everything else is inherited.
 
 ## Install
 
@@ -57,10 +57,15 @@ The `type-enum` rule is set explicitly and is aligned to the estate's release-pl
 
 A `!` marker or a `BREAKING CHANGE:` footer promotes any type to a **major** bump.
 
-Everything else is inherited from `@commitlint/config-conventional` unchanged, including:
+Length rules are pinned explicitly ([A-1413](https://linear.app/rheged-studio/issue/A-1413)) so an upstream change to config-conventional's 100-character defaults cannot silently move the gate:
 
-- a non-empty commit type and subject,
-- the header max-length limit, and
+- `header-max-length` — **72** (error). Counts the whole first line (`type(scope): subject`). Git's usual subject ceiling.
+- `body-max-line-length` — **256** (error).
+- `footer-max-line-length` — **256** (error), so `BREAKING CHANGE:` sentences are not left trapped at 100.
+
+URL lines remain exempt (`/\bhttps?:\/\/\S+/`). Everything else is inherited from `@commitlint/config-conventional` unchanged, including:
+
+- a non-empty commit type and subject, and
 - `defaultIgnores` — merge (`Merge …`), revert (`Revert …`), `fixup!` and `squash!` messages are skipped automatically, so this config never needs to blanket-ignore them by author identity.
 
 ## Bot-authored commits
@@ -76,10 +81,10 @@ Everything else is inherited from `@commitlint/config-conventional` unchanged, i
 
 Dependabot's subjects come from a `commit-message` template in each repo's `.github/dependabot.yml`, which sets `prefix` (plus `prefix-development` for the npm ecosystem) and `include: scope`. Without that template Dependabot falls back to inferring a prefix from recent commit history — which may yield a Conventional subject, but is not guaranteed to, and can leave a bare `Bump …` that would fail the gate. The explicit template is what makes the output deterministic, which is why it is a prerequisite for making the gate a required check rather than an optional nicety ([A-980](https://linear.app/rheged-studio/issue/A-980)).
 
-Two inherited rules are worth knowing when reading a bot commit:
+The length pins are the real ceiling when reading a bot commit:
 
-- **`header-max-length` (100) is the one real ceiling.** This is why Dependabot bumps are grouped — a grouped subject stays short (`bump the actions group with 3 updates`), whereas an ungrouped multi-package subject can run past 100 characters and fail.
-- **`body-max-line-length` (100) ignores unbreakable lines.** Dependabot bodies contain compare URLs well over 100 characters; those pass, because the rule only trips on over-long lines that could have been wrapped. A long prose line still fails.
+- **`header-max-length` (72) is the subject ceiling.** This is why Dependabot bumps stay grouped — a grouped subject stays short (`bump the actions group with 3 updates`), whereas an ungrouped multi-package subject can run past 72 characters and fail. An ungrouped `@rheged-studio/markdownlint-config` bump sits at exactly 72.
+- **`body-max-line-length` and `footer-max-line-length` (256) ignore unbreakable lines.** Dependabot bodies contain compare URLs well over 256 characters; those pass, because the rule only trips on over-long lines that could have been wrapped (`/\bhttps?:\/\/\S+/`). A wrapable prose line still fails above 256.
 
 Should a bot ever need an exception, prefer fixing its commit template. A per-identity `ignores` entry is a documented last resort, not a first move.
 

package/dist/index.d.ts

@@ -7,10 +7,19 @@ import type { UserConfig } from "@commitlint/types";
  * (`reusable-validate-commits.yml`) and the local husky `pre-push` range check —
  * float on the *same* list with zero drift (A-823 / A-979).
  *
- * The config extends `@commitlint/config-conventional` and deliberately retains
- * all of its defaults (header max length, non-empty type/subject, and the
- * `defaultIgnores` for `Merge …` / `Revert …` / `fixup!` / `squash!` messages).
- * Only `type-enum` is overridden.
+ * The config extends `@commitlint/config-conventional` and retains its
+ * non-empty type/subject defaults plus `defaultIgnores` for `Merge …` /
+ * `Revert …` / `fixup!` / `squash!` messages. It pins four rules explicitly so
+ * an upstream change cannot silently move the estate's gate:
+ *
+ * - `type-enum` — the estate's release-aligned types (A-823 / A-979).
+ * - `header-max-length` — 72 (Git's usual subject ceiling; A-1413).
+ * - `body-max-line-length` — 256 (A-1413).
+ * - `footer-max-line-length` — 256, so `BREAKING CHANGE:` sentences are not
+ *   left trapped at config-conventional's 100 (A-1413).
+ *
+ * URL lines remain exempt via `@commitlint/ensure` (`/\bhttps?:\/\/\S+/`).
+ * There is no identity denylist.
  *
  * `type-enum` is set *explicitly* — even though the list currently mirrors
  * config-conventional's own default — so that an upstream change to

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,mBAAmB,CAAC;AAEpD;;;;;;;;;;;;;;;;;;GAkBG;AACH,QAAA,MAAM,MAAM,EAAE,UAqBb,CAAC;AAEF,eAAe,MAAM,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,mBAAmB,CAAC;AAEpD;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,QAAA,MAAM,MAAM,EAAE,UAwBb,CAAC;AAEF,eAAe,MAAM,CAAC"}

package/dist/index.js

@@ -6,10 +6,19 @@
  * (`reusable-validate-commits.yml`) and the local husky `pre-push` range check —
  * float on the *same* list with zero drift (A-823 / A-979).
  *
- * The config extends `@commitlint/config-conventional` and deliberately retains
- * all of its defaults (header max length, non-empty type/subject, and the
- * `defaultIgnores` for `Merge …` / `Revert …` / `fixup!` / `squash!` messages).
- * Only `type-enum` is overridden.
+ * The config extends `@commitlint/config-conventional` and retains its
+ * non-empty type/subject defaults plus `defaultIgnores` for `Merge …` /
+ * `Revert …` / `fixup!` / `squash!` messages. It pins four rules explicitly so
+ * an upstream change cannot silently move the estate's gate:
+ *
+ * - `type-enum` — the estate's release-aligned types (A-823 / A-979).
+ * - `header-max-length` — 72 (Git's usual subject ceiling; A-1413).
+ * - `body-max-line-length` — 256 (A-1413).
+ * - `footer-max-line-length` — 256, so `BREAKING CHANGE:` sentences are not
+ *   left trapped at config-conventional's 100 (A-1413).
+ *
+ * URL lines remain exempt via `@commitlint/ensure` (`/\bhttps?:\/\/\S+/`).
+ * There is no identity denylist.
  *
  * `type-enum` is set *explicitly* — even though the list currently mirrors
  * config-conventional's own default — so that an upstream change to
@@ -20,6 +29,9 @@
 const config = {
     extends: ["@commitlint/config-conventional"],
     rules: {
+        "body-max-line-length": [2, "always", 256],
+        "footer-max-line-length": [2, "always", 256],
+        "header-max-length": [2, "always", 72],
         "type-enum": [
             2, // error
             "always",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rheged-studio/commitlint-config",
-  "version": "1.0.3",
+  "version": "2.0.0",
   "description": "Shared commitlint configuration for Rheged Studio packages.",
   "keywords": [
     "commitlint",