Composer install of 7.6 fails due to reliance on dev package.

[peterwilsoncc]

Composer installs are currently defaulting to Jetpack 7.4.1 due to later packages having @dev dependencies with "minimum-stability": "dev",.

Composer inherits the minimum stability from the parent package.

Steps to reproduce the issue

1. Initialise a composer config
2. Run composer require "automattic/jetpack *"
3. Composer will install from the 7.4 branch as that is the latest branch with stable packages.
4. Run composer require "automattic/jetpack 7.6"
5. Composer will refuse to upgrade as Jetpack uses a dev release:

   
   composer require "automattic/jetpack 7.6"

./composer.json has been updated Loading composer repositories with package information Updating dependencies (including require-dev) Your requirements could not be resolved to an installable set of packages.

Problem 1

• Installation request for automattic/jetpack 7.6 -> satisfiable by automattic/jetpack[7.6].
• automattic/jetpack 7.6 requires automattic/jetpack-connection @dev -> no matching package found.

Potential causes:

• A typo in the package name
• The package is not available in a stable-enough version according to your minimum-stability setting see https://getcomposer.org/doc/04-schema.md#minimum-stability for more details.
• It's a private package and you forgot to add a custom repository to find it

Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

Note: My package does not have a minimum stability setting so the second suggested cause comes from composer default settings. 

#### What I expected
<!-- A clear and concise description of what you expected to happen. -->
Jetpack to install the latest release using stable dependencies. 

#### What happened instead
Jetpack 7.4.1 installed.

[jeherve]

Related: #12680

[stale[bot]]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[jeherve]

We're still working on this. #14964 is what we are currently working on.

[stale[bot]]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[jeherve]

This can now be closed, as it was handled via Changelogger and the autotagger tool added in #19192. Our packages' stable versions now always rely on stable packages.