Skip to content

Pull in the various AI dependencies we'll be using #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 27, 2025
Merged

Pull in the various AI dependencies we'll be using #50

Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9be45b4
Install the Abilities API via composer
dkotter Oct 24, 2025
f4d5ab9
Install the MCP Adapter via composer; install from trunk for now as t…
dkotter Oct 24, 2025
7bd3855
Install the Jetpack Autoloader and load that instead of the composer …
dkotter Oct 24, 2025
3d98c9e
Install the WordPress AI Client via composer
dkotter Oct 24, 2025
5f7b657
Update the Abilities API to the 0.4.0-rc version
dkotter Oct 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 16 additions & 2 deletions composer.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,12 @@
"type": "wordpress-plugin",
"license": "GPL-2.0-or-later",
"require": {
"automattic/jetpack-autoloader": "^5.0",
Copy link
Member

@felixarntz felixarntz Oct 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just chiming in here with a thought (not reason to change anything at all, just something to think about): An alternative to trying to only load one version of the dependency would be to prefix the bundled dependencies.

Benefit: More robust, as it prevents conflicts due to minor differences between different versions if one plugin used an API slightly differently.
Drawback: Code will be "unnecessarily" (at least almost unnecessarily) loaded multiple times, and the initial setup is a little more tricky.

It's certainly a tradeoff. But I'd be inclined to eventually document both as reasonable alternative paths for pulling in and loading those dependencies.

"ext-json": "*",
"php": ">=7.4",
"ext-json": "*"
"wordpress/abilities-api": "^0.3.0",
"wordpress/mcp-adapter": "dev-trunk",
"wordpress/wp-ai-client": "dev-trunk"
},
"require-dev": {
"wp-coding-standards/wpcs": "^3.2.0",
Expand All @@ -26,14 +30,24 @@
"WordPress\\AI\\Tests\\": "tests/"
}
},
"minimum-stability": "dev",
"prefer-stable": true,
"config": {
"allow-plugins": {
"dealerdirect/phpcodesniffer-composer-installer": true
"automattic/jetpack-autoloader": true,
"dealerdirect/phpcodesniffer-composer-installer": true,
"php-http/discovery": true
},
"platform": {
"php": "7.4"
}
},
"repositories": [
{
"type": "vcs",
"url": "https://github.com/WordPress/wp-ai-client"
}
],
"scripts": {
"format": "phpcbf --standard=phpcs.xml.dist",
"lint": "phpcs --standard=phpcs.xml.dist",
Expand Down
Loading