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, 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 is an automated update to the wp-cli/wp-cli framework. It ensures the project uses the most recent version of the WP-CLI core, incorporating any new features, bug fixes, or performance improvements from the upstream repository.

Highlights

• WP-CLI Framework Update: The wp-cli/wp-cli framework has been updated to its latest changeset, reflecting changes in composer.lock.

Changelog

• composer.lock
  • Updated the reference for wp-cli/wp-cli to a newer commit hash.
  • Updated the timestamp for the wp-cli/wp-cli package.

Activity

• This is an automated pull request, indicating no human activity has occurred 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. ↩

[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 new commit reference. However, I've noticed that the timestamp associated with this dependency is set to a future date. This is a data integrity concern that could cause issues with tools that rely on package timestamps and should be investigated in the upstream repository.

[gemini-code-assist]

The time field for the wp-cli/wp-cli package is set to a future date (2026-03-16T17:04:25+00:00). This is highly unusual and likely indicates an issue with the commit metadata in the upstream wp-cli/wp-cli repository, possibly due to a misconfigured system clock. While this pull request is automated, propagating a future timestamp could lead to unexpected behavior in tools that rely on package release dates for dependency resolution or auditing. It is recommended to investigate the source of this future timestamp in the upstream repository.

[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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!