{"version":"2.1.287","anchor":"plugin-update-check-reports-when-the-plugin-directory-is-una","canonical_anchor":"plugin-update-check-reports-when-the-plugin-directory-is-una","heading":"Plugin update check no longer claims up to date when it could not check","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/plugin-update-check-reports-when-the-plugin-directory-is-una","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plugin update check no longer claims up to date when it could not check\n\nWhen the plugin directory is unavailable, the update check now says the plugin was not checked rather than calling it up to date\n\n**What**\n\nWhen Claude Code checks whether a plugin (an add-on) has an update, and the plugin directory it would check against is not available in your session, it now says the plugin \"was not checked for updates\". Before, it always said the plugin was already at the latest version. There is also a new warning for when refreshing that directory fails.\n\n**Why**\n\nYou no longer get told a plugin is up to date when Claude Code never actually looked.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}