Skip to content

docs: update changelog for v2.13.1 #5

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
shenxianpeng merged 3 commits into from
Aug 4, 2026
+13 −0
Merged

docs: update changelog for v2.13.1 #5

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
219eaa4
docs: update changelog for v2.13.1
shenxianpeng Aug 4, 2026
1c43086
docs: drop non-notable config header link from changelog
shenxianpeng Aug 4, 2026
bfee058
chore: Update release date for version 2.13.1
shenxianpeng Aug 4, 2026
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
13 changes: 13 additions & 0 deletions docs/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ below and to the page that documents the feature properly.

| Version | What changed | Documented in |
|---|---|---|
| [2.13.1](#v2131) | JSON output reports the checked value for passing checks | [Output for scripts and CI](example.md#output-for-scripts-and-ci) |

@coderabbitai coderabbitai Bot Aug 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Fix the broken recipe link.

markdownlint-cli2 reports that #output-for-scripts-and-ci is not a valid fragment in docs/example.md. Update the fragment to the actual heading anchor or add a stable explicit anchor.

🧰 Tools
🪛 markdownlint-cli2 (0.23.2)

[warning] 14-14: Link fragments should be valid

(MD051, link-fragments)

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/changelog.md` at line 14, Update the changelog link in the 2.13.1 entry
to reference the actual heading fragment in docs/example.md, or add a stable
explicit anchor there and link to it. Preserve the existing destination section
and link text.

Source: Linters/SAST tools

| [2.13.0](#v2130) | Stable rule IDs in terminal output and JSON | [Rules reference](rules.md) |
| [2.12.0](#v2120) | Author name and email patterns became configurable | [CC101](rules.md#cc101) · [CC102](rules.md#cc102) |
| [2.11.0](#v2110) | AI attribution policy | [Policy guides](guides/policies.md#ai-attribution) |
Expand All @@ -22,6 +23,18 @@ below and to the page that documents the feature properly.
| [2.5.0](#v250) | Organization-wide config with `inherit_from` | [Integrations](guides/integrations.md#across-an-organization) |
| [2.0.0](#v200) | Configuration moved from YAML to TOML — breaking | [Migrating from v1](migration.md) |

## v2.13.1 (2026-08-05) { #v2131 }

### New Features

* **Passed checks report what they checked** — `--format json` and the
`validate_all_detailed()` API now populate `value` on passing checks with
the raw input that was validated (commit subject, branch name, author
name/email, push refs), so tooling such as commit-check-action can show
exactly what passed instead of an empty string. Terminal output is
unchanged.
See PR [#522](https://github.com/commit-check/commit-check/pull/522).

## v2.13.0 (2026-08-04) { #v2130 }

### New Features
Expand Down