What is your question?

We discovered that Conan 2.17 now uses --refetch when checking if a commit is in the remote. Was this intended? Because this creates a hard dependency to Git >=2.36 which broke some of our older pipelines. Maybe it would be possible to fall back to another detection method in case --refetch is not supported.

The problem we're currently facing is with tag commits that are not on any branch. The first check branch -r --contains {commit} fails for obvious reasons. The second check fetch {remote} --refetch --dry-run {commit} works for the orphan tag commit but only on Git >=2.36. I'm also not really sure whether the code was designed for this corner case at all. Is there any other way to verify that orphan tag commits are in the remote (that works on a wide range of Git versions)?

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide