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
refactor(rubygems): Unify fetching via v1 API #23517
refactor(rubygems): Unify fetching via v1 API #23517
Conversation
…rubygems-extract-v1-fetch
…unify-v1-fetching
…vate into refactor/unify-v1-fetching
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.
why do we loose the package caching? otherwise LGTM
I have no idea how to fix coverage regression, Codecov isn't too helpful |
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.
I think we need a global flag to also cache private packages on self-hosted renovate. currently mostly need npm, nuget, helm, docker and terraform. 🙃
Agreed. I think our caching is quite complex, and we rarely cover it in tests. |
🎉 This PR is included in version 36.21.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes
/v1/versions/foobar.json
with additional metadata in/v1/gems/foobar.json
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: