{"version":"2.1.239","anchor":"bundled-file-extraction-error-no-longer-echoes-the-offending","canonical_anchor":"bundled-file-extraction-error-no-longer-echoes-the-offending","heading":"Bundled-file extraction error no longer echoes the offending path","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/bundled-file-extraction-error-no-longer-echoes-the-offending","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Bundled-file extraction error no longer echoes the offending path\n\nA blocked bundled-file extraction no longer echoes the offending path back at you.\n\n**What**\n\nWhen extraction of a bundled file is blocked for trying to escape its target directory, the error is now the fixed text \"bundled file path escapes its extraction dir\" instead of quoting the path back.\n\n**Details**\n\n- Previously the message named the skill and interpolated the rejected path, putting untrusted text into an error string.\n- The guard itself is unchanged; only what it reports changed.\n\n**Evidence**\n\n`bundled file path escapes its extraction dir`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}