Skip to content

Track top WordPress plugin compatibility#374

Merged
adamziel merged 1 commit into
trunkfrom
codex/top-plugin-compatibility-manifest
May 18, 2026
Merged

Track top WordPress plugin compatibility#374
adamziel merged 1 commit into
trunkfrom
codex/top-plugin-compatibility-manifest

Conversation

@adamziel
Copy link
Copy Markdown
Contributor

What it does

Adds a checked-in compatibility target for the current WordPress.org top 100 popular plugins.

The new manifest records, for each ranked plugin:

  • install_support: wp-admin-plugin-install
  • merge_support: generic-audit or semantic-recipe-plus-generic-audit
  • semantic recipe tags where ForkPress already has plugin-shaped validator coverage

Rationale

“Support the top 100 plugins” needs a concrete artifact. Without a manifest, we cannot tell whether a release covers the same target over time or whether a plugin moved from generic audit coverage to semantic validator coverage.

This does not overclaim automatic semantic conflict repair for every plugin. The default support model remains generic DB/file merge plus durable plugin-validator-unchecked audit decisions when an active plugin has no validator.

Implementation

Added scripts/popular-plugin-compat.mjs:

node scripts/popular-plugin-compat.mjs refresh
node scripts/popular-plugin-compat.mjs validate

refresh pulls the WordPress.org popular-plugin API and writes runtime/cow/plugin-compat/popular-wordpress-plugins.json. validate is offline and enforces exactly 100 unique ranked plugins with declared install and merge support policy.

Added docs/top-plugin-support.md and linked it from the docs sidebar and plugin validator docs.

Testing instructions

node scripts/popular-plugin-compat.mjs validate
node --test scripts/popular-plugin-compat.test.mjs
umask 0022 && npm test
umask 0022 && npm run build
git diff --check

Add a WordPress.org popular-plugin manifest with install and merge support policy for the top 100 plugins.

Add an offline validator and docs page so plugin compatibility coverage is explicit and testable.
@adamziel adamziel merged commit a67794b into trunk May 18, 2026
13 checks passed
@adamziel adamziel deleted the codex/top-plugin-compatibility-manifest branch May 18, 2026 19:52
@adamziel adamziel mentioned this pull request May 18, 2026
adamziel added a commit that referenced this pull request May 18, 2026
## Release `v0.1.45`

Version bump and release metadata update for `v0.1.45`.

**Changelog draft:**
* Support remote clone SSH credentials
([#373](#373))
* Track top WordPress plugin compatibility
([#374](#374))
* Add top plugin install smoke
([#375](#375))
* Document remote-site onboarding flow
([#376](#376))

**Full changelog:**
v0.1.44...release/v0.1.45

## Next steps

1. **Review** the changes in this pull request.
2. **Push** any additional edits to this branch (`release/v0.1.45`).
3. **Merge** this pull request to publish `v0.1.45`.

Merging will automatically build ForkPress binaries, create a GitHub
release, and update the Homebrew formula.

Co-authored-by: Codex <codex@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants