What's Changed in v2.22.1
Bug fixes
- A zip file written behind a prefix which was removed together with its whole first entry, like a self-extracting page whose first entry is the face shown by the host, is read again: the entries are shifted to their real positions and their data can be read. Since v2.21.0, the shift was decided on the first central directory record only, and a first record whose local file header lies in the removed bytes proves nothing, so the entries kept their stored offsets and
getData()failed withERR_LOCAL_FILE_HEADER_NOT_FOUND, whatever thestrictnessoption. The reader now checks the following records until one settles the question, and keeps the protection against a damaged end of central directory record whose local file headers are right - An entry which lies before the start of the zip file after such a shift is no longer reported as
WARNING_UNSORTED_CENTRAL_DIRECTORY
Full Changelog: v2.22.0...v2.22.1
Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com