-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Docker release notes #2395
Comments
Because docker registries have no metadata for source repo, I can’t think of any solution except hardcoding mappings within Renovate from docker image to GitHub repo. Also in many cases the user probably prefers release notes from the true source (eg node.js repo) than the image source/wrapper. |
What would be better than nothing is checking if there's a matching GitHub repository (or a Gitlab repository on a configurable list of Gitlab instances?) and using that, because often the names line up. For example:
I also wouldn't mind configuring a list of patterns and mappings once, and then not have to go hunt for release notes anymore. For example, a list of regular expressions that turns the image names into repository URLs. That would cover more unusual registries like The Docker Hub also supports automatic builds where you can find a link to the source repository on the page for the Docker image. |
First step we should support that vcs-url schema in case anyone's using it. Next step is we can code in some known mappings (guesses). Final step would be to allow manual overrides like we have for npm and pypi. Note: I'm considering to move this manual mapping into lib/datasource/index.js to avoid reimplementing it in each individual datasoure. |
🎉 This issue has been resolved in version 14.39.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The text was updated successfully, but these errors were encountered: