n8n | n8n@2.22.4

n8n n8n@2.22.4 released on 27-05-2026


n8n n8n@2.22.4 is out now. The runtime no longer aggressively deletes temporary directories during binary-file renames, preventing race conditions and potential data loss when workflows handle binary attachments or large files.

Full details and the code compare are on GitHub: https://github.com/n8n-io/n8n/compare/n8n@2.22.3…n8n@2.22.4. Release metadata is available via the GitHub API: https://api.github.com/repos/n8n-io/n8n/releases/latest.

What’s in this release

  • Removed aggressive temp directory cleanup during binary-data rename (fixes issue #31165; commit 978840d).
  • Prevents race conditions and missing or corrupted binary outputs when nodes stream, move or rename files during execution.
  • Full compare and changes available on GitHub: https://github.com/n8n-io/n8n/compare/n8n@2.22.3…n8n@2.22.4.

Upgrade notes

  • No breaking changes expected. Recommended to upgrade if you process binary attachments or run workflows that rename or move files; monitor a few workflow runs after upgrading and report any regressions with workflow details.
  • If you encounter problems, report them on GitHub with the failing workflow and reference issue #31165 and commit 978840d when filing.

Share any comments or regressions you see on the project issue tracker or community channels so maintainers can validate the fix.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes