n8n n8n@2.32.5 released on 24-07-2026
n8n n8n@2.32.5 is out now. It fixes S3 signing so object keys containing spaces and other reserved characters are encoded with strict RFC 3986 rules, preventing signature mismatches for authenticated S3 requests.
See the GitHub compare view and commit 95ad6f6 for the exact changes and review links: https://github.com/n8n-io/n8n/compare/n8n@2.32.4…n8n@2.32.5
What’s in this release
- Core S3 signing updated to use strict RFC 3986 encoding for object paths (fixes issue #34871; implemented in commit 95ad6f6).
- Addresses signature mismatches for object keys that require percent-encoding (for example, spaces encoded as %20 rather than +), improving compatibility with AWS S3 signing expectations.
- Small, non-breaking maintenance patch that passed usual PR review tooling (stage-review badge and auto-generated Cubic review links are included in the release notes).
Upgrade notes
- If you run workflows that create, read or sign S3 object URLs (S3 nodes, integrations or custom code relying on n8n’s S3 signing), upgrade to n8n@2.32.5 and test S3-dependent workflows that use keys with spaces or other non-alphanumeric characters.
- No breaking changes are expected; if you need to roll back, the previous tag is n8n@2.32.4 — review the compare view and commit history before reverting.
If you upgrade, please share whether the change resolved S3 signing failures for your workflows and any edge cases you encounter.
