{"version":"2.1.193","anchor":"plugin-renaming-in-marketplace-manifests","canonical_anchor":"plugin-renaming-in-marketplace-manifests","heading":"Plugin Renaming in Marketplace Manifests","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.193\/e\/plugin-renaming-in-marketplace-manifests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.193","markdown":"### Plugin Renaming in Marketplace Manifests\n\n**What**\n\nMarketplace authors can now declare plugin renames in their manifest using a `renames` field. When a plugin is not found under its old name, Claude Code follows the rename chain and migrates the user's settings to the new name automatically.\n\n**Details**\n\n- The `renames` field is an append-only map of old plugin name \u2192 current name (or `null` to indicate the plugin was removed).\n- On plugin-not-found, the loader resolves the chain and updates `enabledPlugins` and `pluginConfigs` in all writable settings files.\n- A new `tengu_plugin_renamed` telemetry event tracks rename outcomes (`resolved`, `removed`, `unresolved`).\n- Unresolvable renames (cycles, missing targets, chains deeper than the limit) are logged with the reason.\n\n**Evidence**\n\nNew `renames` schema field (search for `\"Append-only map of old plugin name\"`) and rename migration logic (search for `\"migrateRenamedPluginsInSettings\"`)"}