14.9.1

Fixes a conversion loop in multi-storage setups, where sibling rows named the wrong storage and the async queue refilled with the same entries forever.

Fixed

• Sibling rows in sys_file_processedfile now record the storage that actually holds the sibling; where a storage keeps its processing folder in another storage, the row named the processing folder's storage while the file sat next to the original, so the extension never found it again and reconverted the image on every render, refilling the async queue with the same entries forever (#121).
• A storage that is not enabled for siblings — set to Disabled, or a non-Local driver left on Auto — no longer gets siblings written next to its originals and no longer collects queue entries; the setting was previously only read for the processing folder's storage, so a storage keeping that folder elsewhere was written to regardless.

On upgrade: rows written by earlier versions correct themselves the first time each image is rendered again, at the cost of one extra conversion per affected file. If a storage with a non-Local driver relied on siblings being written next to its originals, set Generate WebP / AVIF / JPEG XL siblings to Enabled on that storage record — webp:diagnose lists the storages that are silently off.

Full changelog: 14.9.0...14.9.1