Update wp-cli framework

[schlessera]

This is an automated pull-request

Updates the wp-cli/wp-cli framework to the latest changeset.

[gemini-code-assist]

Summary of Changes

Hello @schlessera, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs an automated update of the wp-cli/wp-cli framework to its most recent version. This ensures that the project remains current with the upstream dependency, incorporating any new features, bug fixes, or performance improvements from the framework. The change primarily involves updating the locked version reference and its associated timestamp in the Composer lock file.

Highlights

• Dependency Update: The wp-cli/wp-cli framework dependency has been updated to its latest changeset, specifically changing the Git reference from 578b600f5eb46eb05c7aeb24e8415b998f8ee4b0 to b95c2d0037c1541a341f6416d37f8f8d8a9e69be.
• Timestamp Refresh: The time metadata for the wp-cli/wp-cli package in composer.lock was updated from 2026-02-19T08:47:41+00:00 to 2026-02-20T13:01:32+00:00, reflecting the recent update.

Changelog

• composer.lock
  • Updated the Git reference for the wp-cli/wp-cli package.
  • Refreshed the timestamp for the wp-cli/wp-cli package entry.

Activity

• This is an automated pull request, and no human activity has been recorded yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

Hello! 👋

Thanks for opening this pull request! Please check out our contributing guidelines. We appreciate you taking the initiative to contribute to this project.

Contributing isn't limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation.

Here are some useful Composer commands to get you started:

• composer install: Install dependencies.
• composer test: Run the full test suite.
• composer phpcs: Check for code style violations.
• composer phpcbf: Automatically fix code style violations.
• composer phpunit: Run unit tests.
• composer behat: Run behavior-driven tests.

To run a single Behat test, you can use the following command:

# Run all tests in a single file
composer behat features/some-feature.feature

# Run only a specific scenario (where 123 is the line number of the "Scenario:" title)
composer behat features/some-feature.feature:123

You can find a list of all available Behat steps in our handbook.

[gemini-code-assist]

Code Review

This pull request is an automated update for the wp-cli/wp-cli framework dependency. The changes in composer.lock reflect the latest commit from the dev-main branch. My review identified a recurring issue with the commit timestamp from the upstream repository, which is set to a future date. While this is unlikely to be a critical bug, it points to a process issue that should be investigated to ensure data integrity.

[gemini-code-assist]

The time field for the wp-cli/wp-cli package is set to a future date. The previous timestamp was also in the future, which suggests this is a recurring issue. This likely indicates a persistent clock misconfiguration in the environment where the upstream commits are created. Incorrect metadata can cause unpredictable behavior in tools that rely on timestamps for caching or other logic. It is recommended to investigate and fix the source of these future-dated commits in the wp-cli/wp-cli repository to ensure data integrity.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!