hooks: version floor says `rtk rewrite` came in 0.23.0; it came in 0.25.0

Open Beginner friendly
#5,126 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
shell, typescript

Research direction

Grep hooks/ for 0.23.0 and for MIN_SUPPORTED_RTK_MINOR; the constant and its two messages live in hooks/pi/rtk.ts, and the version guards sit in hooks/claude/rtk-rewrite.sh and hooks/cursor/rtk-rewrite.sh. First confirm the claim against CHANGELOG.md and commit f447a3d before changing anything. Done means the floor reads 25, every warning/README line matches, and a re-grep of hooks/ returns no stale 0.23.0 references.

Written by the indexing model from the issue text.

Description

area:docs bug good first issue priority:low

The Pi extension and the legacy shell hooks gate on rtk >= 0.23.0 "when rtk rewrite was introduced":

  • hooks/pi/rtk.ts: header comment, MIN_SUPPORTED_RTK_MINOR = 23, the two "need >= 0.23.0" messages
  • hooks/claude/rtk-rewrite.sh and hooks/cursor/rtk-rewrite.sh: Requires: line, version guard comment and warning
  • hooks/README.md ("rtk version too old (< 0.23.0)"), hooks/claude/README.md, hooks/cursor/README.md

rtk rewrite first shipped in 0.25.0: commit f447a3d (feat: rtk rewrite — single source of truth for LLM hook rewrites (#241)) is not an ancestor of v0.24.0 and is first contained in v0.25.0, and CHANGELOG.md lists it under 0.25.0. #3918 reports that the v0.23.0 and v0.24.0 release binaries answer rtk rewrite "git status" with exit 2 and empty stdout.

Nothing breaks today, because every one of these hooks passes the command through on a non-0/3 exit, so 0.23.0 and 0.24.0 fall open. The floor and its messages are still wrong: a user on 0.24.0 is told their rtk is recent enough and gets no rewrites. The fix is the floor (23 → 25) and the wording in the files above.

Dominant language
Rust
Stars
86.4k
Forks
5.5k
Avg merge
6d 18h
Merged PRs (30d)
51

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rtk-ai/rtk

All issues in rtk-ai/rtk

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.