n8n 2.26.7 - Compression Node Stability Patch for Legacy Branch

The 2.26.7 release is a backport of the Compression node correction into the 2.26 release track: the node will now decompress only actual archive members. Backporting this kind of fix across active release branches is important for organizations that have staggered upgrade cycles or strict change-control policies preventing immediate moves to newer major releases.

For businesses, the practical effect is reduced risk of workflow failures stemming from malformed or unexpected input files. Automated processes that integrate file ingestion, ETL, or user uploads are especially sensitive to decompression behavior - a single erroneous extraction can cause downstream parsing errors, increased storage usage, or prolonged processing times.

Action items for operations teams: patch environments running 2.26.x, then exercise file-handling workflows with a suite of archive and non-archive payloads. Update CI tests to include negative cases (non-archive inputs) and resource-constraint scenarios. If you operate multi-tenant instances, prioritize tenants whose workflows involve large or untrusted uploads.

Finally, take this as a governance cue to document which runtime nodes handle potentially hazardous operations (compression, execution, file I/O). That inventory will accelerate triage and patch prioritization in future maintenance cycles and reduce reliance on emergency fixes.