{"version":"2.1.285","anchor":"dependency-resolution-and-semver-picking-fixes","canonical_anchor":"dependency-resolution-and-semver-picking-fixes","heading":"Fix for picking the best matching version of a dependency","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/dependency-resolution-and-semver-picking-fixes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Fix for picking the best matching version of a dependency\n\nA version lookup compared the wrong value and never found the best matching version; it now compares the right one\n\n**Unclear.** Which feature, plugins or something else, uses this version lookup is not stated.\n\n**What**\n\nClaude Code has code that picks which version of a plugin or dependency to use. It works out the highest version that fits the requested range, then looks it up. The lookup compared against the wrong value, so it could never find a match. It now looks up the version it actually chose.\n\n**Why**\n\nBefore this fix, the matching version was never selected, so this lookup always came back empty.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}