[feature] select latest recipe revision matching client version

If currently a recipe is updated on the remote index, the new revision will be automatically selected independent of the conan client version. This is especially a problem if the newer recipe is no longer compatible with an older conan client. In this case, it is displayed that the recipe requires a newer client version or in the worst case that some imports cannot be found (because the min. conan version is usually after the imports in the recipe).

Wouldn’t it be better to not select always the latest but the latest compatible recipe revision?

This would probably require that instead of _resolve_latest_ref either all are resolved (probably inefficient because the recipes must all be fetched?) or conan starts from the latest one and continues with older ones if the checked one is incompatible: https://github.com/conan-io/conan/blob/develop/conans/client/remote_manager.py#L105

Is there currently another alternative than updating conan or locking the recipe revisions?

• I’ve read the CONTRIBUTING guide.

[codetent]

Ok thank you for your suggestions! I guess for now I’m probably going with the second approach as it is for now the simplest approach … and I’m looking forward to see the first stable release of conan 2.0 with all the changes 😃

[codetent]

Just a follow up question for specifying the recipe revision in the recipe: does this also work for build requirements (with override)?