n8n 2.29.11 - Backport Fix: Separate Execution Visibility from License Sharing

For organizations maintaining the 2.29 maintenance line, release 2.29.11 brings parity with fixes applied in newer branches: execution visibility is decoupled from the license-sharing toggles. This is particularly important for enterprises that run long-term supported releases and need stable access semantics for logs and workflow histories.

The business import is the same as on newer branches - execution visibility should be a governance and permission setting, not an accidental side-effect of licensing choices. Restoring that separation supports compliance efforts (e.g., audit trails and e-discovery), reduces friction for incident responders, and prevents business process disruption caused by changing license feature flags.

Teams should treat this patch as a signal to re-evaluate their access matrices and any compensating controls they deployed when the coupling existed. If your organization relied on automated exports or monitoring workarounds because execution visibility was limited, determine whether those can be simplified or retired. Additionally, include this check in release governance so backports remain consistent across branches.

Operational recommendations: (1) apply the patch to maintenance environments and validate role-based access to executions; (2) brief compliance and SRE teams on the restored behavior; and (3) update internal policies to avoid using license configuration as a proxy for access control.