N8N Update 3.78.1 - Non working python interpreter

[BrutalBirdie]

Regarding the latest N8N Upgrade 3.78.1 to 1.86.1.
Anyone elso here who used the python interpreter that is now not working?

Cannot find module '/app/code/file:/app/code/node_modules/src/js/pyodide.asm.js' imported from /app/code/node_modules/pyodide/pyodide.mjs

{
  "errorMessage": "Cannot find module '/app/code/file:/app/code/node_modules/src/js/pyodide.asm.js' imported from /app/code/node_modules/pyodide/pyodide.mjs",
  "errorDetails": {},
  "n8nDetails": {
    "nodeName": "Code",
    "nodeType": "n8n-nodes-base.code",
    "nodeVersion": 2,
    "n8nVersion": "1.86.1 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "Error: Cannot find module '/app/code/file:/app/code/node_modules/src/js/pyodide.asm.js' imported from /app/code/node_modules/pyodide/pyodide.mjs",
      "    at finalizeResolution (node:internal/modules/esm/resolve:265:11)",
      "    at moduleResolve (node:internal/modules/esm/resolve:933:10)",
      "    at defaultResolve (node:internal/modules/esm/resolve:1169:11)",
      "    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)",
      "    at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)",
      "    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)",
      "    at ModuleLoader.import (node:internal/modules/esm/loader:472:34)",
      "    at defaultImportModuleDynamicallyForModule (node:internal/modules/esm/utils:214:31)",
      "    at url (node:internal/modules/esm/utils:253:12)",
      "    at loadScript (file:///app/code/node_modules/src/js/compat.ts:219:69)"
    ]
  }
}

But since Cloudron did not touch much I assume it is an upstream issue.
https://git.cloudron.io/packages/n8n-app/-/compare/v3.78.0...v3.78.1?from_project_id=768

Ahhh found the upstream issue:
https://github.com/n8n-io/n8n/issues/14479

broken since 1.86
last working version 1.85.4

Please upgrade to 1.86.1 or 1.87.2 to get the fix for this

note: 1.87.2 is a pre-release, so we just have to wait

Just that the forum knows, this is a known issue.