n8n n8n@2.29.8 released on 08-07-2026
n8n n8n@2.29.8 is out now. It fixes an execution-redaction crash caused by null run‑data slots and limits automatic database connection recovery to Postgres, so redaction completes reliably and non‑Postgres backends no longer get unnecessary reconnection attempts.
See the n8n repository on GitHub for the full release notes and compare view: https://github.com/n8n-io/n8n/compare/n8n@2.29.7…n8n@2.29.8
What’s in this release
- Guard against null run‑data slots in execution redaction (fix from #33726) to avoid crashes when sensitive data is being redacted.
- Run database connection recovery only for Postgres (fix from #33753) to prevent incorrect recovery behaviour for other database backends.
- Release published 2026-07-08 with GitHub compare link and stage-review and Cubic automated review badges for maintainers and reviewers (see compare: https://github.com/n8n-io/n8n/compare/n8n@2.29.7…n8n@2.29.8).
Upgrade notes
- No breaking changes are listed in the release notes; these are targeted bug fixes — follow your normal update procedure and review the compare for code-level differences.
- If you need to roll back, use your existing deployment rollback process; the release notes do not provide specific rollback instructions.
Share any comments or issues on the n8n GitHub (see the linked compare and issue references) and tell the project if these fixes affect your workflows.
