티스토리 수익 글 보기

티스토리 수익 글 보기

Update to the latest release of the WP AI Client by dkotter · Pull Request #118 · WordPress/ai · GitHub
Skip to content

Update to the latest release of the WP AI Client #118

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

Jump to bottom
Merged
jeffpaul merged 1 commit into from
Dec 1, 2025
Merged

Update to the latest release of the WP AI Client #118

jeffpaul merged 1 commit into from
Dec 1, 2025

Conversation

@dkotter
Copy link
Collaborator

@dkotter dkotter commented Dec 1, 2025 •
edited
Loading

What?

Closes #117

Pulls in the latest release of the WP AI Client

Why?

We were using an older version of the WP AI Client and the latest release includes a fix from the PHP AI Client when using Google as your AI provider. Also hardcoding to a specific release (0.1.1) instead of pulling from trunk so we can have more control over when updates are pulled in.

How?

Updates our composer.json file to pull in the 0.1.1 release and also updates composer.lock with those changes

Testing Instructions

  1. Checkout this PR
  2. Run composer install
  3. Ensure things install correctly
  4. Ensure you still see an AI Credentials settings page
  5. Ensure you can add credentials for Google and those work

@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 <dkotter@git.wordpress.org>
Co-authored-by: aslamdoctor <aslamdoctor@git.wordpress.org>

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

@dkotter dkotter mentioned this pull request Dec 1, 2025
Closed
6 tasks
@codecov
Copy link

codecov bot commented Dec 1, 2025 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 29.61%. Comparing base (5c4491a) to head (d49b3d7).
⚠️ Report is 5 commits behind head on develop.

Additional details and impacted files 
@@            Coverage Diff             @@
##             develop     #118   +/-   ##
==========================================
  Coverage      29.61%   29.61%           
  Complexity       145      145           
==========================================
  Files             14       14           
  Lines            878      878           
==========================================
  Hits             260      260           
  Misses           618      618
Flag Coverage Δ
unit 29.61% <ø> (ø)

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.

@jeffpaul jeffpaul merged commit e9e2720 into WordPress:develop Dec 1, 2025
22 of 23 checks passed
@dkotter dkotter mentioned this pull request Dec 1, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jeffpaul jeffpaul jeffpaul approved these changes

Assignees

@dkotter dkotter

Labels

None yet

Projects

None yet

Milestone

0.1.1

Development

Successfully merging this pull request may close these issues.

Getting 404 error while generating title

2 participants

@dkotter @jeffpaul