Add version upgrade notification at session start

[calreynolds]

Summary

• Adds a non-blocking version check that runs via Claude Code SessionStart hook
• Compares local installed version against latest on GitHub, notifies user if an update is available
• Results cached for 24 hours to avoid repeated network requests
• Silent on any failure (offline, timeout, missing files)

How it works

check_update.sh runs at session start. Its stdout is injected as context Claude sees, so it naturally relays the upgrade notice to the user before proceeding with their request.

Supports all install paths:

• Plugin mode: reads $CLAUDE_PLUGIN_ROOT/VERSION
• Project-scoped install: reads .ai-dev-kit/version in project dir
• Global install: reads ~/.ai-dev-kit/version

What users see

When outdated (once per new session, max once per 24h network check):

╔══════════════════════════════════════════════════════════════╗
║                                                             ║
║   Databricks AI Dev Kit — update available!                 ║
║                                                             ║
║   Installed:  v0.1.2                                        ║
║   Available:  v0.1.3                                        ║
║                                                             ║
║   To upgrade, run:                                          ║
║   bash <(curl -sL https://raw.githubusercontent.com/        ║
║     databricks-solutions/ai-dev-kit/main/install.sh)        ║
║                                                             ║
╚══════════════════════════════════════════════════════════════╝

When up to date or offline: nothing.

Files changed

• .claude-plugin/check_update.sh (new) — version check script with 24h cache
• hooks/hooks.json (modified) — added check_update hook to SessionStart

Test plan

• Install v0.1.2 in a temp folder, start Claude Code session — should see upgrade banner
• Start another session — should still see banner (cached, versions still differ)
• Update to v0.1.3, clear cache, start session — should see nothing
• Disconnect from network, clear cache, start session — should see nothing (silent fail)
• For install.sh users: add hook to .claude/settings.json pointing to check_update.sh

🤖 Generated with Claude Code

[malcolndandaro]

Test Report

Tested all scenarios locally. 7/8 passed, 1 minor issue found.

Test	Description	Result
1	Outdated version (local=0.0.1, remote=0.1.3) — shows banner	PASS ✅
2	Up-to-date version (local=remote=0.1.3) — silent	PASS ✅
3	Cache reuse on second run — no redundant network call	PASS ✅
4	Network failure (unreachable URL) — silent exit	PASS ✅
5	Missing VERSION file (all env vars → empty temp dir) — should be silent	FAIL ❌
6a	Project-scoped install path ($CLAUDE_PROJECT_DIR/.ai-dev-kit/version)	PASS ✅
6b	Global install path (~/.ai-dev-kit/version)	PASS ✅
6c	Plugin mode path ($CLAUDE_PLUGIN_ROOT/VERSION)	PASS ✅

Issue 1: Fallback path prevents "missing VERSION" scenario (Low)

check_update.sh, line 16 — The 4th candidate resolves ../VERSION relative to BASH_SOURCE, so even when all env vars point elsewhere, the script always finds the repo's own VERSION file. The early-exit on line 23 is effectively unreachable while the script lives inside the repo. Minor edge case, but worth being aware of.

Issue 2: Banner box alignment (Cosmetic)

check_update.sh, lines 60-61 — The ║ right border uses hardcoded padding, so version strings of different lengths (e.g. 0.0.1 vs 0.1.10) will break the box alignment. Since Claude interprets this as context rather than terminal output, this is low priority.

Verdict

Core functionality works well across all install paths. Caching, silent failures, and version comparison all behave as expected. Good to merge with optional fixes for the above.

---

This comment was generated with GitHub MCP.

[malcolndandaro]

LGTM, not merging as @dustinvannoy-db might want to have a look