Declare the WordPress version we actually test against - #14
Open
henry-mosh wants to merge 1 commit into
Open
Conversation
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 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Plugin Check flags
Tested up to: 7.0now that WordPress 7.1 is current. The penalty isn't cosmetic — the directory drops plugins from search results when this header trails the current release.readme.txt:Tested up to: 7.0→7.1. One line.Why this is recording a fact, not making a claim
composer.lockis gitignored, so CI resolves^7.0fresh on every run — the "WP latest" matrix jobs have been installing and passing against 7.1 since it shipped. The last green run onmain(33779439820) logsLocking roots/wordpress-no-content (7.1).Also verified locally against 7.1 before changing the header:
bin/local-rig.sh verifygreen end to end — this one matters most here, since 7.1 is ≥6.9 and so exercises core's template-enhancement output buffer rather than the pre-6.9 callback fallbackphpcsandcomposer lintcleanNote on the live listing
This ships with 1.2.0, which is still held pending the app-side production deploy. The currently published 1.1.2 also declares
Tested up to: 7.0, so the live listing is carrying the search penalty right now. That's fixable independently with a readme-only SVN update and doesn't need to wait for this release.🤖 Generated with Claude Code