n8n n8n@2.39.6 released on 16-09-2026
n8n n8n@2.39.6 is out now. It fixes an issue where Gateway credit eligibility was being evaluated against the wrong sub-node, which could cause incorrect gating or credit behaviour for certain workflows.
See the release on GitHub or the n8n documentation for full details, upgrade instructions and the compare link between n8n@2.39.5 and n8n@2.39.6.
What’s in this release
- Bug fix: Check Gateway credits eligibility against the correct sub-node to prevent incorrect gating or credit behaviour in some workflows.
- Feature: Add a v3 breaking-change rule that flags the planned storage directory rename so admins can find and plan for affected workflows and configurations.
- Feature: Runtime warning when the deprecated N8N_DB_PING_TIMEOUT environment variable is used; prompts users to update to the supported DB ping timeout setting.
Upgrade notes
- Storage directory rename is marked as a v3 breaking change — search for references to the old storage directory and plan migration steps before upgrading to n8n v3.
- N8N_DB_PING_TIMEOUT is deprecated and now emits a runtime warning; replace it with the supported DB ping timeout setting and consult the configuration docs to avoid future breakage.
- Rollback: if you need to revert, you can roll back to n8n@2.39.5 (see the release compare for details).
Share any comments on your upgrade experience or report issues on the n8n GitHub or community channels.
