{"version":"2.1.323","anchor":"plugin-update-to-a-specific-older-version-and-a-tag-aware-u","canonical_anchor":"plugin-update-to-a-specific-older-version-and-a-tag-aware-u","heading":"Plugin updates can target a specific older version or tag","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-update-to-a-specific-older-version-and-a-tag-aware-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugin updates can target a specific older version or tag\n\nPlugin updates can now aim at a specific older version or tag instead of always the latest one\n\n**Unclear.** It is not clear whether any command lets you ask for a specific plugin version yet.\n\n**What**\n\nUpdating a plugin can now aim at a specific version or tag, and compares it with the version you have installed. Before, an update always went to the latest version in the catalog. New messages cover the cases where the installed plugin is already past the requested version, or was not updated to that version. Update messages can also carry an extra note.\n\nTwo smaller changes come with it:\n\n- Installing a plugin's dependencies is now skipped in some cases.\n\n- The separate handling for disabled npm marketplaces has been removed.\n\n**Why**\n\nThis looks like groundwork for pinning a plugin to a version or rolling back to an earlier one.\n\n- Area: Plugins\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}