{"version":"2.1.224","anchor":"plugins-enabled-only-by-repo-settings-are-no-longer-auto-ins","canonical_anchor":"plugins-enabled-only-by-repo-settings-are-no-longer-auto-ins","heading":"Plugins enabled only by repo settings are no longer auto-installed and recorded","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/plugins-enabled-only-by-repo-settings-are-no-longer-auto-ins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Plugins enabled only by repo settings are no longer auto-installed and recorded\n\nA plugin switched on by repo settings alone is no longer installed into your own records.\n\n**What**\n\nA plugin turned on solely by settings committed in the repository you opened is no longer written into your own plugin installation records. Previously a project or local settings file could get a plugin auto-installed on your behalf. Plugins backed by your own config are unaffected.\n\n**Details**\n\n- Skipped entries are logged with the reason that they were enabled only by repo-authored settings.\n\n**Evidence**\n\n`Skipped auto-recording `\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}