n8n n8n@2.33.3 released on 31-07-2026
n8n n8n@2.33.3 is out now. It fixes import failures for security-audit risk reporter files that include a file extension and ensures the MCP Server Trigger Node only saves execution data after a tool call has completed, so execution records are consistent.
See the n8n GitHub release for full details, the compare view and the embedded StageReview and Cubic review badges.
What’s in this release
- Core: Import security-audit risk reporters with a file extension (issue #35275, commit 6a71142) — prevents import errors and missing reporter behaviour.
- MCP Server Trigger Node: Save execution data only after tool call completes (issue #35284, commit 77271fa) — avoids truncated or premature execution snapshots.
- Release metadata and review tooling badges included: release date, compare link (n8n@2.33.2…n8n@2.33.3) plus StageReview and Cubic review badges for quick QA access.
Upgrade notes
- No breaking changes are listed in this patch; if you experienced reporter import failures or incomplete MCP execution records, upgrade to n8n@2.33.3. See the compare page: https://github.com/n8n-io/n8n/compare/n8n@2.33.2…n8n@2.33.3
- No specific rollback instructions appear in the release notes; revert to your previous deployment procedure if a rollback is required.
Share any feedback or problems you see on the n8n GitHub issues or the release thread so others can benefit from your experience.
