Best practices for tagging requirements in both WP & CP plugin directories?

I’m preparing to migrate one of my WordPress blogs to ClassicPress. I have a plugin that I wrote for it that’s in the WordPress plugin directory and I’d like to submit it to the ClassicPress directory once I’ve verified that it works.

I’d prefer to just use one code repository for both, but including both sets of requires/tested headers in one Readme seems like it might get confusing.

Required: 1.0
Tested: 1.4
Requires at least: 4.0
Tested up to: 5.9

I assume the directories themselves will only use the fields specific to WP or CP, but it’s not very human-readable.

How do most ClassicPress plugin developers handle this scenario?

Hi @Kelson and welcome.

There is active work in ClassicPress to improve support for themes and plugins, including enabling uploads from zip files and better compatibility checks. Ultimately the headers can all be included in the plugin or theme main file rather than in the readme.

We currently don’t have a specific header for declaring compatibility with CP, but that is something I’ve been thinking about more and more in recent time.