{"version":"2.1.227","anchor":"plugin-names-starting-with-a-dot-or-matching-the-sync-direct","canonical_anchor":"plugin-names-starting-with-a-dot-or-matching-the-sync-direct","heading":"Plugin names starting with a dot, or matching the sync directory, are rejected","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/plugin-names-starting-with-a-dot-or-matching-the-sync-direct","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Plugin names starting with a dot, or matching the sync directory, are rejected\n\nPlugin names starting with a dot or matching the sync root are now rejected.\n\n**What**\n\nPlugin-name validation now rejects names beginning with `.` and names that fold to the reserved spelling used for the plugin sync root, with an explanation that such directories are never picked up as plugins. Previously only path separators were checked.\n\n**Details**\n\n- Backed by a new shared module of name-safety helpers covering reserved-name folding and Windows reserved device names.\n\n**Evidence**\n\n`those directories are never loaded as plugin adoptions`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}