orbit-release-meta

WordPress plugin release metadata validation requires checking plugin headers, readme.txt files, version parity, license compliance, and RTL stylesheet presence. Running a gauntlet script against the plugin path automates these pre-release checks for WP.org submission readiness.

A WordPress plugin readme.txt check involves validating the file structure, verifying version parity with the main plugin header, confirming license compliance, checking POT file freshness, and ensuring RTL stylesheet presence to meet WP.org submission standards.

Yes, you can automate WordPress plugin header validation by executing a gauntlet script with a quick mode flag against your plugin path. This automatically verifies header completeness, readme.txt validity, and license compliance before tagging a release.

WordPress plugin submission metadata validation fails when plugin headers are incomplete, readme.txt files lack valid structure, version numbers mismatch between files, or license compliance and RTL stylesheet presence requirements are not met.

Yes, you need direct access to plugin files and WP.org submission standards to check WordPress release metadata. The validation process reads local plugin directories to verify headers, readme.txt, version parity, and POT file freshness accurately.