{"version":"2.1.228","anchor":"plugin-installs-can-no-longer-explode-through-symlinks","canonical_anchor":"plugin-installs-can-no-longer-explode-through-symlinks","heading":"Plugin installs can no longer explode through symlinks","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/plugin-installs-can-no-longer-explode-through-symlinks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Plugin installs can no longer explode through symlinks\n\nPlugin installs stop at 20,000 files or 512MB so symlink loops cannot fill your disk.\n\n**What**\n\nCopying a plugin directory now runs against a budget of 20,000 entries and 512 MB. A plugin that materialises more files than that through symlinks fails with \"Plugin materializes more files through symlinks than the copy budget allows\" instead of filling the disk.\n\n**Details**\n\n- The copier takes an explicit dereference flag and threads a shared budget accumulator through the walk.\n- Symlinks pointing at ancestor directories and cyclic targets are skipped and logged rather than followed.\n\n**Evidence**\n\n`Plugin materializes more files through symlinks than the copy budget allows`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}