Well, you’re right. But making a little dummy change like raising the compatibility flag does not make the plugin “maintained” by strict definition … Frankly, it also doesn’t really make it worse than just ignoring warnings.
The next release 2.4.0 is currently in preparation (finally, after 3 years). We can try to push forward a final test round. (GitHub release PR with beta package, if someone’s curious to try it: https://github.com/pluginkollektiv/cachify/pull/303)
If there’s no movement by end of the week I will give 2.3 a quick test with WP 6.6 and maybe just raise the compatibility if there’s no reason against. (I won’t do it blindly)
-
This reply was modified 1 year, 10 months ago by
Stefan Kalscheuer. Reason: add GitHub release reference
I’m a big fan of Cachify, and I understand your answer, it’s logical. I appreciate your effort. I look forward to hearing more from you. GOOD LUCK!
Cachify 2.4.0 was release today after a few weeks of additional testing and last minute corrections. If you experience any issues with the update please let us know.
Congratulations on the release of 2.4.0. There are some fantastic changes there.