n8n n8n@2.40.6 released on 24-09-2026
n8n n8n@2.40.6 is out now. It restores reliable OpenTelemetry export after restarts when Sentry is enabled, fixes instance reporting that crosses the UTC midnight boundary, and adds certificate-based authentication for instance reports, improving telemetry and reporting reliability for self-hosted, licensed installations.
Read the full release notes and changelog on the n8n GitHub compare page: https://github.com/n8n-io/n8n/compare/n8n@2.40.5…n8n@2.40.6
What’s in this release
- Bugfix: Keep OpenTelemetry export working after a restart when Sentry is enabled so traces continue to be exported across restarts.
- Bugfix: Retry instance reports that cross the UTC midnight boundary, preventing missed or failed reports around the day boundary.
- Feature: Authenticate instance reports with the instance license certificate so reports are signed/authenticated for improved security.
Upgrade notes
- No breaking changes are listed in the release notes; see the GitHub compare page for details: https://github.com/n8n-io/n8n/compare/n8n@2.40.5…n8n@2.40.6
- Administrators using licensed or self-hosted installations should ensure the instance license certificate is available so instance reporting can authenticate successfully. If you need to revert, roll back to n8n@2.40.5.
If you upgrade, share any comments or issues on your experience so others can see whether the fixes resolve traces and reporting in similar setups.
