Update required WordPress Version

[masteradhoc]

What?

Based on our readme we support the latest two WP releases.
With the release of 6.9 (12.2025) this means we support 6.8 and 6.9.
This PR updates the version number in the plugin header.

Changelog Entry

Changed - Update the minimum required WordPress Version to 6.8

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: masteradhoc <masteradhoc@git.wordpress.org>
Co-authored-by: kasparsd <kasparsd@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[kasparsd]

Considering that we don't have a practical reason to bump the WP core requirement (in my testing across the networks of WP that I run), I would prefer to have more people using this plugin at an up-to-date version than limit that purely because of the update cadence.

[masteradhoc]

@kasparsd yeah fully see your point. just if we have those requirements i think we should regularely also do those upgrades as our tests also wont cover old WP versions. But in my opinion users of this plugin - interested in securing their site - probably anyway would run a old version.

[kasparsd]

Yeah, that's a tricky thing. I personally see the upgrade/dependency policy mostly as a guide of what to expect from the plugin. So if at some point we need to bump the WP/PHP requirement because of some feature or practical requirement, we could do it in a way that is predictable and understandable to everyone.

Also agree that it is very likely that sites using an older WP core would also run outdated plugins. Even the usage graph here somewhat confirms that only 62% of plugin users run the latest version of the plugin.

[masteradhoc]

@kasparsd yeah probably if the WP version is not getting updated also the plugin is left behind. Totally understand your point here. If you want feel free to merge, if you want to wait another plugin release with this one its also not an issue for me at all.

[kasparsd]

@jeffpaul What are your thoughts on this? Should we bump the WP/PHP requirements as early as possible or delay them, if possible?