Repository navigation
craftkit v1.53.0
Update notice on session start
npm never tells an installed package's users that a new version exists, and craftkit has
no CLI they run, so a release reached only the people who went looking for it.
hooks/craftkit-update-check.jsruns on Claude CodeSessionStart. It reads the
installed version from~/.craftkit-state/version(written by every sync), asks the npm
registry for the latest at most once a day, and shows a one-line notice with the update
command when the registry is newer. The answer is cached in
~/.craftkit-state/update-check; a failed fetch is cached too, so an offline machine
pays the 1.5s timeout once a day rather than every session.- Any failure stays silent.
CRAFTKIT_UPDATE_CHECK=offturns it off. check.shcheck 24a runs the hook against a seeded cache: a notice for a newer
version, none for an equal or older one, none when switched off.- Only reaches installs from this version on: anyone on v1.52.0 or older needs one manual
update before they see notices.