Mutasem Aldmour ff8bc0aa7b fix(core): Stop the Python import guidance pointing at deployment config ... On managed deployments the import allowlist is not the user's to change, so an agent that names `N8N_RUNNERS_STDLIB_ALLOW` or tells them their setting is invalid only produces a support request about something nobody will change for them. Cloud also runs task runners in external mode, where n8n cannot see the runner's configuration at all, so that guidance was doubly unfounded there. Every agent- and user-facing surface now states the capability and stops: assume no imports, write import-free Python, or use JavaScript. Environment variables survive only in code comments and the config class, where operators read them. The external-mode and rejected-allowlist cases now share one message. They led to the same action already, and the separate wording existed only to name the setting behind each. Tests pin the rule across every policy shape rather than the phrasing, so a future edit cannot quietly reintroduce a config recommendation. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-08-27 15:47:56 +02:00
..
JavascriptCodeDescription.ts	fix(core): Prevent workflow builder from making HTTP requests in Code nodes (no-changelog) (#32084)	2026-06-11 12:08:06 +00:00
PythonCodeDescription.ts	fix(core): Stop the Python import guidance pointing at deployment config	2026-08-27 15:47:56 +02:00