fix(CMS-3090): mark WordPress 7.1 as tested, add License plugin header

[fabianwgl]

User description

Summary

WordPress.org shows "Compatibility with WordPress 7.1.1: Not tested" for 4.7.3 because readme.txt still says Tested up to: 7.0. A customer is asking for a timeline (Zendesk 464674).

JIRA: CMS-3090

This matters more than the label suggests. WordPress Plugin Check reports it as an error: "This means your plugin will not show up in searches" until "Tested up to" matches the current WordPress version.

What changed

• readme.txt: Tested up to: 7.0 → 7.1. WordPress.org only compares major.minor, so this covers 7.1.1, 7.1.2 and later 7.1.x releases.
• cookiebot.php: adds License: GPLv2 or later and License URI to the plugin header. This clears the Plugin Check plugin_header_no_license error. readme.txt already declared the license; the plugin file didn't. No behavior change.

No version bump. The plan is to ship this as a readme-only update: update readme.txt in SVN trunk and in tags/4.7.3. The header change goes out with the next regular release.

Testing

Ran a local Docker smoke test (@wordpress/env, PHP 8.1, WP_DEBUG on). Each WordPress version was tested with both the WordPress.org 4.7.3 zip and a zip built from master:

WordPress	WordPress.org zip	master zip
7.0.6	PASS	PASS
7.1.2 (latest)	PASS	PASS
7.2-alpha-63879 (nightly, no beta yet)	PASS	PASS

What each run checked:

• Front end: banner loader script present with the correct settings ID; no PHP errors.
• cookiebot/cookie-declaration block: renders cd.js on the front end and is registered in the editor as API v3.
• Admin pages (Dashboard, Settings, Support, Plugins/addons, PPG): all return 200 with no PHP errors.
• debug.log: no warnings, notices or deprecation messages.
• WP-CLI: wp cookiebot status and wp cookiebot verify return clean results.

Re-ran on this branch against WordPress 7.1.2: all PASS, and Plugin Check no longer reports outdated_tested_upto_header or plugin_header_no_license.

Not covered: Cookiebot-mode (UUID) IDs, multisite, individual addons, the consent click flow.

Follow-ups (not in this PR)

• Bitbucket usercentricscode/wordpress-plugin needs the same change.
• After merge: SVN readme update to trunk and tags/4.7.3.
• Existing Plugin Check findings, the same on every WordPress version (backlog):
  • 71 files have no ABSPATH guard.
  • 41 register_setting() calls have no sanitize callback.
  • "Requires at least: 4.4", but the code uses functions from 4.5 and 4.7.
  • The readme has 15 tags, but WordPress.org only uses the first 5.

Test plan

• Smoke test on WordPress 7.0.6, 7.1.2 and 7.2-alpha (local Docker)
• Plugin Check clean for outdated_tested_upto_header and plugin_header_no_license
• CI passes
• After merge: SVN readme update to trunk and tags/4.7.3, then confirm WordPress.org shows "Tested up to 7.1"

---

CodeAnt-AI Description

Update WordPress compatibility information and plugin licensing details

What Changed

• WordPress.org now lists the plugin as tested with WordPress 7.1
• The plugin header now clearly identifies the GPLv2-or-later license and its official license page

Impact

✅ Accurate WordPress 7.1 compatibility status
✅ Fewer WordPress.org plugin validation warnings
✅ Clearer plugin licensing information

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	ee5d5d8	Sep 23, 2026 · 13:10	13:11

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[qodo-code-review]

PR Summary by Qodo

Mark WordPress 7.1 compatibility and declare plugin license

🐞 Bug fix 📝 Documentation ⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Marks plugin version 4.7.3 as tested with WordPress 7.1.
• Adds required GPL license metadata to the main plugin header.
• Resolves two Plugin Check errors affecting WordPress.org discoverability.

High-Level Assessment

The PR uses the canonical WordPress metadata fields consumed by WordPress.org and Plugin Check. Updating the existing headers directly is the minimal and correct approach; runtime compatibility work or additional abstractions are unnecessary because smoke testing found no behavioral issues.

Files changed (2) +3 / -1

Bug fix (1) +1 / -1

readme.txtMark the plugin as tested through WordPress 7.1 +1/-1

Mark the plugin as tested through WordPress 7.1

• Raises the WordPress.org “Tested up to” value from 7.0 to 7.1. This covers WordPress 7.1.x releases and clears the outdated compatibility-header finding that can reduce plugin search visibility.

readme.txt

Other (1) +2 / -0

cookiebot.phpDeclare GPL license in the WordPress plugin header +2/-0

Declare GPL license in the WordPress plugin header

• Adds the GPLv2-or-later license name and GNU license URL to the main plugin header. This aligns the executable plugin metadata with the existing readme declaration and clears the Plugin Check missing-license error.

cookiebot.php

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can keep summaries lean with Finding overflow, which tucks the rest behind 'View more'

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud