You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hook auto-update: warn when rtk-rewrite.sh is outdated #344
Won't benefit from any future rewrite rule changes without manual rtk init -g
There's no mechanism to detect or update stale hooks. Users stay on the old version silently.
Proposal
Add a hook version check on rtk startup:
Add a version comment at the top of the hook: # rtk-hook-version: 2
On startup (or on rtk rewrite), check the installed hook file
If the hook is outdated (missing version tag or old version), print a one-line warning to stderr:
[rtk] Hook outdated — run `rtk init -g` to update
Show the warning at most once per day (marker file, same pattern as telemetry)
Why not auto-patch?
The hook file lives in user space (~/.claude/hooks/). Silently modifying it could break custom modifications. A warning is safer and lets the user decide when to update.
Activity
feat: warn when installed hook is outdated (#344)
feat: warn when installed hook is outdated (#344)
feat: warn when installed hook is outdated (#344)
feat: warn when installed hook is outdated (#344)
feat: warn when installed hook is outdated (#344) (#350)
fix: bugs #196 #344 #345 #346 #347 — gh --json, hook check, RTK_DISAB…
feat: warn when installed hook is outdated (rtk-ai#344) (rtk-ai#350)
test: add smoke tests for rewrite, verify, proxy, discover, diff, wc,…
fix: prettier false positive when not installed (#221) (#359)
feat: warn when installed hook is outdated (rtk-ai#344) (rtk-ai#350)
fix: bugs rtk-ai#196 rtk-ai#344 rtk-ai#345 rtk-ai#346 rtk-ai#347 — gh…
fix: prettier false positive when not installed (rtk-ai#221) (rtk-ai#359