Skip to content

Conversation

@dkotter
Copy link
Collaborator

@dkotter dkotter commented Dec 1, 2025

What?

Ensure the right version of the PHP AI Client is pulled in from the WP AI Client update

Why?

In #118, I updated our composer config to pull in the latest release of the WP AI Client package (0.1.1) instead of pulling in trunk. This was supposed to pull in the latest release of the PHP AI Client (0.2.1) but it seems that just running the composer require wordpress/wp-ai-client:0.1.1 command didn't pull in the downstream dependencies so it was still using the 0.2.0 release of that package.

How?

Initially tried running composer update to bring in everything but there appears to be some conflicts with our PHPCS tools coming out of recent changes made to the develop branch of the phpcompatibility/php-compatibility package. So instead of trying to fix all of those, I ran composer require wordpress/wp-ai-client:0.1.1 -W to bring in the updated version of the PHP AI Client package (the -W flag was the trick here)

Testing Instructions

n/a

@dkotter dkotter added this to the 0.2.0 milestone Dec 1, 2025
@dkotter dkotter self-assigned this Dec 1, 2025
@github-actions
Copy link

github-actions bot commented Dec 1, 2025

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: dkotter <[email protected]>

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

@dkotter dkotter requested a review from jeffpaul December 1, 2025 21:40
@codecov
Copy link

codecov bot commented Dec 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 28.79%. Comparing base (4bbc5ea) to head (f84b1c1).
⚠️ Report is 9 commits behind head on develop.

Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #122      +/-   ##
=============================================
- Coverage      29.37%   28.79%   -0.59%     
- Complexity       145      153       +8     
=============================================
  Files             14       14              
  Lines            885      903      +18     
=============================================
  Hits             260      260              
- Misses           625      643      +18     
Flag Coverage Δ
unit 28.79% <ø> (-0.59%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dkotter
Copy link
Collaborator Author

dkotter commented Dec 1, 2025

Worth noting that in testing with Google Gemini, I'm now getting a timeout error instead of the original 404 error. This will be fixed once a new release of the WP AI Client goes out as the default timeout value was increased in WordPress/wp-ai-client#29.

So we could hold on this PR until the 0.2.0 release of the WP AI Client package is ready and then update to that here

Copy link
Member

@jeffpaul jeffpaul left a comment

Choose a reason for hiding this comment

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

Let's at least fix this version bump for this and can come back and do another, proper bump when the WP client hits 0.2.0?

@jeffpaul jeffpaul merged commit 611e69a into WordPress:develop Dec 1, 2025
21 of 23 checks passed
@dkotter dkotter deleted the update/wp-ai-client branch December 1, 2025 22:31
@dkotter dkotter mentioned this pull request Dec 8, 2025
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants