From 3d02d755309ab2806e0849963c1a4bbe27577ade Mon Sep 17 00:00:00 2001 From: rotorsoft Date: Thu, 5 Feb 2026 10:39:52 -0500 Subject: [PATCH] chore: disable commitlint body/footer line length limits Completed GitHub issue #5 Semantic-release generates commit messages with release notes in the body that can exceed 100 characters per line. The Co-Authored-By footer can also exceed this limit. Disabled body-max-line-length and footer-max-line-length rules to prevent CI failures during releases. Co-Authored-By: Claude --- commitlint.config.js | 3 +++ progress.txt | 6 ++++++ 2 files changed, 9 insertions(+) diff --git a/commitlint.config.js b/commitlint.config.js index 99cf23f..b7b1d5f 100644 --- a/commitlint.config.js +++ b/commitlint.config.js @@ -20,5 +20,8 @@ export default { ], "subject-case": [2, "always", "lower-case"], "header-max-length": [2, "always", 100], + // Disable body/footer line length limits for semantic-release notes + "body-max-line-length": [0, "always", Infinity], + "footer-max-line-length": [0, "always", Infinity], }, }; diff --git a/progress.txt b/progress.txt index d84db24..5475548 100644 --- a/progress.txt +++ b/progress.txt @@ -16,3 +16,9 @@ Each entry documents: date, feature, decisions, files changed, tests, and concer - Changes: Configured semantic-release with changelog/npm/git plugins, added commitlint with conventional commits, set up husky commit-msg hook, created CI/release workflows, wrote comprehensive README and AGENT.md - Decisions: Used pnpm-compatible husky v9, semantic-release v24 with standard plugins, commitlint strict mode for subject-case - Issues: None + +[2026-02-05] #5 chore: Configure semantic-release commit message line length limits +- Files: commitlint.config.js +- Changes: Disabled body-max-line-length and footer-max-line-length rules to allow semantic-release notes and Co-Authored-By footers +- Decisions: Set rules to severity 0 (disabled) rather than increasing limit to avoid arbitrary caps +- Issues: None