New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Conan package revisions #16467
Comments
i think this can be handled as digest update, like we do for docker images digests |
Hi there, Get your issue fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. To get started, please read our guide on creating a minimal reproduction. We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment. Good luck, The Renovate team |
Hey , Here is the minimal reproduction repo: https://github.com/segretil/renovate-conan-revisions Tell me if you need anything else, I can add a CI to it if you want. Thank you |
Reproduction forked to https://github.com/renovate-reproductions/16467 |
Next step is to confirm if we can get the revision from the existing API calls we make |
🎉 This issue has been resolved in version 32.155.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What would you like Renovate to be able to do?
I would like renovate to support Conan package revisions. Those are really useful in order to have robust reproducible builds. Indeed, if you do not specify the revision for a specific package, one version may address multiple binaries for a given profile.
For example, here is a
conanfile.txt
:this may refer to mutiple packages for the same profile as you can see here : https://conan.io/center/opus?version=1.3.1&revision=6d2446ed5a38e86a3bb304db3ffb3e01
That is why people start using more and more revisions, that way the
conanfile.txt
becomes:and here only one package is referenced for one profile.
What I would like renovate to do, is to update the revision when a newer one is available.
For example when I am writing this, the revision
5132ab8db7b69dd8e26466e0b3b017dd
is newer so I would expect renovate to submit this patch:If you have any ideas on how this should be implemented, please tell us here.
The revisions can be obtained with the
conan search
command.For example, if I want to know all the revisions for
opus/1.3.1@_/_
onconancenter
, I can doconan search --revision opus/1.3.1@_/_ -r=conancenter
which gives me this:Here are the logs (https://docs.conan.io/en/1.46/mastering/logging.html) of this call:
So maybe the route
<url>/v2/conans/<package_name>/<version>/<user>/<channel>/revisions
can be used to achieve that if I am not mistaken.Thank you for your time :)
Is this a feature you are interested in implementing yourself?
Maybe
EDIT: Minimal reproduction: https://github.com/segretil/renovate-conan-revisions
The text was updated successfully, but these errors were encountered: