{"version":"2.1.280","anchor":"plugin-metadata-now-tracks-git-commit-sha-and-claudeai-serv","canonical_anchor":"plugin-metadata-now-tracks-git-commit-sha-and-claudeai-serv","heading":"Plugin metadata now tracks and checks git commit SHA","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/plugin-metadata-now-tracks-git-commit-sha-and-claudeai-serv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Plugin metadata now tracks and checks git commit SHA\n\nInstalled plugins now record their git commit SHA, and a helper can check whether all copies of a plugin agree on it\n\n**What**\n\nInstalled plugin records now carry more git-related metadata, and there's a new way to check consistency across multiple installs of the same plugin.\n\n- When resolving an installed plugin's info, the code now also copies over `gitCommitSha` and a `serverPluginId` (taken from a `claudeaiPluginId` field), guarded by path-matching and an id-validity check.\n\n- A new helper looks up all installed instances of a named plugin, optionally filtered by scope, and returns their shared `gitCommitSha` only if every instance is on the same commit; otherwise it returns undefined.\n\n**Why**\n\nTracking the exact commit a plugin was installed from, and being able to detect when different installs of the same plugin have drifted apart, helps catch inconsistent or outdated plugin installations.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}