{"version":"2.1.319","anchor":"plugin-dependencies-resolved-after-explicit-plugin-update-a","canonical_anchor":"plugin-dependencies-resolved-after-explicit-plugin-update-a","heading":"Updating a plugin now installs its missing dependencies","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/plugin-dependencies-resolved-after-explicit-plugin-update-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Updating a plugin now installs its missing dependencies\n\nWhen you update a plugin, Claude Code now installs any missing dependencies and adds a note about them to the update message\n\n**What**\n\nWhen you update a plugin, Claude Code now checks what other plugins it depends on, installs any that are missing, and adds a note to the update message. Before, an update did no dependency step at all.\n\n- If the check fails, the note says the plugin's dependencies could not be checked.\n\n- If non-essential network traffic is turned off, the note says: \"Dependencies are not installed while non-essential traffic is turned off.\"\n\nAutomatic plugin updates also reuse the list of plugins already installed on disk when working out dependencies, instead of reading it again.\n\n**Why**\n\nAn updated plugin that needs something new gets it, and the message tells you when that did not happen.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}