{"version":"2.1.277","anchor":"plugin-gitcommitsha-resolution-gains-a-marketplace-npm-fallb","canonical_anchor":"plugin-gitcommitsha-resolution-gains-a-marketplace-npm-fallb","heading":"Plugin gitCommitSha resolution gains a marketplace-npm fallback","tier":"internal","area":"Plugin Install","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/plugin-gitcommitsha-resolution-gains-a-marketplace-npm-fallb","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Plugin gitCommitSha resolution gains a marketplace-npm fallback\n\nPlugin version tracking gets a fallback for npm-based marketplaces without a git checkout\n\n**What**\n\nWhen Claude Code figures out which version of a plugin's code is installed (by resolving a git commit hash, used for caching), it now handles the case where the plugin's checkout isn't a git repository but comes from an npm-style plugin marketplace. In that case, it falls back to a separate resolver to find a commit-like identifier. A new `keepStoredCommit` flag also ensures that if neither method can resolve an identifier, a previously stored one isn't discarded.\n\n**Why**\n\nThis prevents plugins installed from npm-based marketplaces from losing their version-tracking information just because they weren't installed via a plain git checkout, and avoids erasing a known-good stored version when a fresh lookup comes up empty.\n\n- Area: Plugin Install\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}