Version 1.43.0

The WebP and AVIF copies an image optimizer places beside the originals are now resolved back to the file they were made from.

Optimizers record foo.jpg.webp and foo-300x200.webp nowhere, so until now every attachment-based decision saw them as unknown files.
They follow their source everywhere: the derivative of a published size is public, the derivative of the protected original stays protected, and the content-aware mode treats them as the post’s own image.
A replaced-extension derivative whose source is ambiguous — foo.jpg and foo.png existing as different attachments — stays unresolved on purpose, and unresolved falls to the protected side.