Feature request: backtrack parent version when minimumReleaseAge blocks a transitive dependency

[ensconced]

I would like to request a feature for installs that use minimumReleaseAge.

Current behavior

When dependency resolution hits a transitive package that has no mature version satisfying a selected parent's range, pnpm fails with:

ERR_PNPM_NO_MATURE_MATCHING_VERSION

Example:

• A depends on B via ^ range
• latest compatible B introduces/updates dependency on C
• no mature C version satisfies B's C range yet
• install fails

Requested behavior

When minimumReleaseAge is enabled and this happens, try fallback/backtracking to an older compatible version of the parent package (B) that still satisfies A's range, if that allows a fully mature dependency graph.

In other words: prefer a resolvable mature graph over hard failure when an older compatible parent can avoid the blocked transitive.

Would this make sense? Maybe as an opt-in via a new config option?