Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Tinify

    (@tinify)

    Hi Matt, Yes, that was a failure on our side. We missed updating the plug-in header when releasing the latest version. This will be straightened out on the next release (3.6.9). We also took steps within our release automation to prevent this from happening again. Apologies for the inconvenience!

    Plugin Author Tinify

    (@tinify)

    Hi Matt,

    We have updated our plugin to version 3.6.9 and the aforementioned issue should be fixed. Thanks again for your patience!

    • This reply was modified 5 months, 2 weeks ago by Tinify.
    Thread Starter WFMattR

    (@wfmattr)

    Thanks!

    -Matt R

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.