Packages for stable2409-1 are missing

[pandres95]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Description of bug

I'm getting the following error (same with all the crates' versions listed below) when trying to update to stable2409-1 using psvm:

    Updating crates.io index
error: failed to select a version for the requirement `emulated-integration-tests-common = "^14.1.0"`
candidate versions found which didn't match: 14.0.0, 13.0.0, 11.0.0, ...
location searched: crates.io index
required by package `asset-hub-kusama-emulated-chain v1.0.0 (/Users/**/**/runtimes/integration-tests/emulated/chains/parachains/assets/asset-hub-kusama)`

The main reason behind this issue is that these versions seem to be missing from crates.io.

Packages affected

• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]

Steps to reproduce

I ran the update using this command:

psvm --version stable2409-1

pvsm bumped the versions to some crates (at least 6 or 7 of them). After that, I started getting those cargo errors, just to find out that those versions didn't exist at all on crates.io. 😅

When trying to update to stable2409, it worked out perfectly fine (see runtimes#490). But failed when trying to update to stable2409-1 (here).

[clangenb]

So the patch publishing for not the most recent stable is mostly broken due to a version conflict on crates IO for the most recent stable, see polkadot-fellows/runtimes#493 (comment).

Wouldn't the solution to this be to just simply bump minor versions whenever a new stable version is released? Then the patch versions can be reserved for patches to the individual stable releases. I know this would kind a break the semantic versioning, but I think it is a very simple fix that helps us actually releasing patches on crates.io for older stable versions.

[acatangiu]

@ggwpez @EgorPopelyaev @Morganamilo this is high priority IMO, looks like we have a broken patch release mechanism potentially blocking properly delivering security fixes or other high priority fixes.