A nonexistant `wp-cli/wp-cli` 2.13.0 is required

[circlecube]

Bug Report

• Yes, I reviewed the contribution guidelines.
• Yes, more specifically, I reviewed the guidelines on how to write clear bug reports.

Describe the current, buggy behavior

We have v2.7.0 required in a project, and want to update to 2.7.2 for the #488 fix. Composer is not able to update the package since it requires wp-cli-wp-cli 2.13, but that version doesn't seem to have been released. Checking https://github.com/wp-cli/wp-cli/releases confirms and lists 2.12.0 released May '25. I'm a bit confused why this i18n-command package updated the wp-cli dependency to 2.13 if it doesn't exist, am I missing something?

The issue: wp-cli/wp-cli skipped v2.13 entirely — it's going from v2.12.0 directly to v3.0 (currently 3.0.x-dev, not yet a stable release). So ^2.13 is an unreachable constraint and this i18n-command package update is unatainable.

_

I assume since wp-cli v3 is pending that the 2.13.0 release was either skipped or missed due to focus on v3. v3 is not yet a stable release though, so hesitant to update to that version in our project, and are stuck with either a known bug, or updating to an unstable version.

I just wanted to call this out in case it's a quick/easy fix to tag a 2.13.0 while 3.0 work progresses.

[swissspidy]

We renamed 2.13 to 3.0 which is the imminent upcoming release. You can pre-test it using wp cli update --nightly, or use an older version of i18n-command in the meantime. I know it's a bit confusing.

[circlecube]

Ah, I looked for a duplicate but not a closed one. Thanks for the update - I'll try to be patient for a stable release ;)