From 94db6a9e7cb076b5eaefaff4a0b75d55e88946df Mon Sep 17 00:00:00 2001 From: henry-idingo Date: Thu, 3 Sep 2026 18:50:10 +0200 Subject: [PATCH] Declare the WordPress version we actually test against MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plugin Check flags `Tested up to: 7.0` now that 7.1 is current, and the penalty is not cosmetic: the directory drops plugins from search results when this header trails the current release. The header was stale rather than untrue. `composer.lock` is gitignored, so CI resolves `^7.0` fresh on every run — the "WP latest" matrix jobs have been installing and passing against 7.1 since the day it shipped (run 33779439820 locks `roots/wordpress-no-content (7.1)`). Confirmed locally too, on 7.1: 382 tests green across core, WooCommerce and multisite, plus the end-to-end rig, which is the one that exercises 7.1's own template enhancement buffer rather than the pre-6.9 fallback. So this records a fact that was already true, rather than making a claim ahead of the evidence. Co-Authored-By: Claude Opus 5 --- readme.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.txt b/readme.txt index 9d9f9a7..65e6d6d 100644 --- a/readme.txt +++ b/readme.txt @@ -2,7 +2,7 @@ Contributors: citecue Tags: ai, ai-crawlers, gptbot, ai-seo, woocommerce Requires at least: 5.8 -Tested up to: 7.0 +Tested up to: 7.1 Requires PHP: 7.4 Stable tag: 1.2.0 License: GPLv2 or later