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
fix(datasource/docker): Artifactory next link is broken for tags api #20745
fix(datasource/docker): Artifactory next link is broken for tags api #20745
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How exactly will this "fall back" to normal behavior once it's fixed?
@rarkins I've validated that the manually constructed next link matches what should be returned in the API call so it won't break if/when Jfrog fixes it. I could add further validation to check if the next link is actually broken by checking for the missing virtual path. Thoughts? |
Co-authored-by: Rhys Arkins <rhys@arkins.net>
It would be nice if this could fall back to using a fixed (correct) path once one is served, but I don't consider it mandatory to accept this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
failed tests
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
🎉 This PR is included in version 34.157.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
@setchy FYI on this artifactory fix for another bug. |
…enovatebot#20745) Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Changes
Context
This has been tested against repo: https://github.com/chezsmithy/openjdk-replacement
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: