Release Plugin Check 1.8.0

[davidperezgar]

This PR prepares the release of Plugin Check version 1.8.0, introducing AI-powered features, enhanced security checks, and improved user experience.

🎯 What's New in 1.8.0

Major Features

🤖 AI-Powered Plugin Namer Tool
A new tool that helps plugin authors evaluate plugin names before submission, checking for trademark conflicts, similarity to existing plugins, and compliance with naming guidelines. The tool provides instant feedback with actionable suggestions. (Note: Requires AI provider configuration; provides guidance only, subject to final review by WordPress.org Plugins team)

🔒 Enhanced Security Checks

• Direct File Access check to ensure proper ABSPATH constant usage
• AI Instructions Detection to prevent development-only files in production builds

📊 Export & Filtering Capabilities

• Export check results in CSV, JSON, and Markdown formats
• Filter results by type (Errors/Warnings) for better focus

Improvements

• Validation of "Tested up to" header matching between plugin file and readme.txt
• Updated trademark check rules with improved flexibility
• Heredoc syntax detection (nowdoc allowed)

Bug Fixes

• WordPress Playground integration compatibility
• WP-CLI plugin slug detection for path-based checks

📝 Documentation

• Updated readme.txt with Plugin Namer tool description and disclaimer
• Updated docs/checks.md with new checks
• Added complete changelog for version 1.8.0

✅ Testing

All tests passing: PHPUnit, PHPCS, PHPStan, and manual testing completed.

📋 Requirements

• WordPress 6.4+
• PHP 7.2+

[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: davidperezgar <davidperez@git.wordpress.org>
Co-authored-by: frantorres <frantorres@git.wordpress.org>
Co-authored-by: ernilambar <nilambar@git.wordpress.org>

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