docs: update changelog for v2.13.1 - #5
Conversation
Add the v2.13.1 entry covering the checked-value reporting in JSON output (#522) and the commit-check.com link in the config header (#524), plus the Highlights row.
✅ Deploy Preview for commit-check ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 56 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. 📝 WalkthroughWalkthroughThe changelog adds a v2.13.1 highlight and release section. It documents validated values in passing JSON output and Changesv2.13.1 release documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with 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.
Inline comments:
In `@docs/changelog.md`:
- 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.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
|
||
| | 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) | |
There was a problem hiding this comment.
📐 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
A comment link in the generated cchk.toml template does not change user-visible behavior and is below the changelog's bar for notable changes.
1 participant
What
Adds the v2.13.1 entry to the changelog:
--format jsonandvalidate_all_detailed()now report the checked value on passing checks (PR commit-check/commit-check#522)