Can't run release scripts

[ethanclevenger91]

Composer version 2.8.6 2025-02-25 13:03:50
PHP version 8.3.17 (/usr/bin/php8.3)

satispressl@mxe-satispressl-live-prod:~/public/wp-content/plugins/satispress$ composer run prepare-for-release
> composer install
No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
Loading composer repositories with package information
GitHub API limit (60 calls/hr) is exhausted, could not fetch https://api.github.com/repos/cedaro/wp-test-suite/tags?per_page=100. Create a GitHub OAuth token to go over the API rate limit. You can also wait until 2025-03-20 23:26:01 for the rate limit to reset.
...
Token stored successfully.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires wp-cli/i18n-command dev-main -> satisfiable by wp-cli/i18n-command[dev-main].
    - wp-cli/i18n-command dev-main requires wp-cli/wp-cli ^2.12 -> found wp-cli/wp-cli[dev-main, 2.12.x-dev (alias of dev-main)] but it does not match your minimum-stability.

Script composer install handling the prepare-for-release event returned with error code 2

I was piloting a feature branch but I'm not able to install Composer dependencies, nor run the release scripts, because the dependencies can't be resolved. Is this expected? Am I missing something?

[bradyvercher]

Nope, not expected. I haven't installed without composer.lock in awhile, so didn't run into that. You can lock that package down to a specific version first:

composer require --dev wp-cli/i18n-command:^2.6