marketplace.json plugin version stuck at 1.1.9 — plugin installs can't receive the update the banner advertises (0.1.14)

[t2tea-niranjan]

Summary

.claude-plugin/marketplace.json still declares plugin version 1.1.9 — unchanged since #443 (April 9) — while the repo VERSION has advanced several times since, now 0.1.14 (#578). Claude Code's plugin updater gates on the marketplace-declared version, so every plugin consumer gets:

$ claude plugin update databricks-ai-dev-kit@databricks-ai-dev-kit
✔ databricks-ai-dev-kit is already at the latest version (1.1.9).

…and never receives new content. Meanwhile check_update.sh — running from the stale installed snapshot — compares its baked VERSION against main and prints the update banner at every session start, advertising an update that cannot be obtained through the plugin path:

║   Databricks AI Dev Kit — update available!
║   Installed:  v0.1.13
║   Available:  v0.1.14

Knock-on effects:

• The banner recommends the standalone curl | bash installer — the wrong remedy for plugin consumers, since it creates a second out-of-band install alongside the plugin.
• The Hotfix: reword update-check hook to remove prompt-injection-style framing #578 banner-rewording fix is itself unreachable for plugin users; they still run the old wording.
• Several VERSION bumps have shipped under the same plugin version, so "1.1.9" snapshots taken on different dates contain different content — the plugin version no longer identifies what's installed.

Observed with Claude Code 2.1.217 on macOS; plugin snapshot from Jul 15 contains VERSION 0.1.13.

Request

Bump the plugin version in .claude-plugin/marketplace.json (e.g. → 1.1.10) so claude plugin update re-snapshots and plugin installs pick up 0.1.14 — this silences the banner (local VERSION then matches main) and delivers #578 to plugin users:

   "metadata": {
     "description": "Official Databricks AI Dev Kit plugin marketplace",
-    "version": "1.1.9"
+    "version": "1.1.10"
   },
   "plugins": [
     {
       "name": "databricks-ai-dev-kit",
       "source": "./",
       "description": "Databricks development toolkit with 19 skills and MCP tools for direct Databricks operations",
-      "version": "1.1.9"
+      "version": "1.1.10"
     }
   ]

Going forward, consider coupling the marketplace.json bump to any VERSION bump (release checklist or CI check) so plugin consumers track releases automatically.

Happy to send this as a PR instead, but CONTRIBUTING.md states external contributions aren't accepted — hence the issue.

Generated with Workspace