docs: bump the install pins to the released version - #14
Conversation
docs-sync has been failing since v2.13.2: the pre-commit snippets on five pages still pin v2.13.1, so anyone copying one installs three releases behind the page describing it. That is the drift the test was written to catch. The blog's pin is left alone, as the test intends -- a dated post records what was current when it was written. Verified against origin/main: the same five failures reproduce there, so this predates and is independent of #13.
✅ 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: 57 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. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
2 participants
docs-syncis red onmain, and has been since v2.13.2 shipped.Five pages pin
rev: v2.13.1in their pre-commit snippets while the released version is 2.13.4, so anyone copying a snippet installs three releases behind the page describing it. This is exactly the driftTestDocumentedRevisionswas written to catch — its own docstring says "a release would leave five pages pinned to the version before it" — and the bump was missed for 2.13.2, 2.13.3 and 2.13.4.example.md,configuration.md,index.md, andguides/integrations.md(twice) →v2.13.4.docs/blog/posts/configuring-commit-check.mdkeeps itsv2.6.0. The test skipsblog/deliberately: a dated post records what was current when it was written, and moving its pin forward would falsify it.Not caused by #13
Checked rather than assumed. I ran the assertion against a clean
origin/mainworktree withinstalled = "2.13.4", and got the same five failures — so it predates #13 and is independent of it. #13 touches onlychangelog.mdandrules.md, neither of which contains arev:pin.Splitting it out rather than folding it into #13, since a release-hygiene chore and a rule's documentation are different changes. #13 will go green once this lands and it picks up
main.One thing worth deciding separately
This will go stale again the moment 2.14.0 is tagged, because the test compares against whatever is installed. Three releases in a row missed it, which suggests the bump wants to be part of the release process rather than something a human remembers. Happy to open an issue for that if you want it tracked — I have not, since it is a change to how you release rather than a docs fix.
🤖 Generated with Claude Code
https://claude.ai/code/session_01U9zFxq8V4qxG4aMzJhGBFn
Generated by Claude Code