-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[chore] change completely how dependabot generates entries #27269
Conversation
7fd3bf6
to
cf047e3
Compare
cf047e3
to
8074088
Compare
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.
Sounds like a pretty good idea 👍 . The code LGTM as well
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.
LGTM, just a small clarification on a magic number
"github.com/google/go-github/v53/github" | ||
"go.opentelemetry.io/collector/confmap/provider/fileprovider" | ||
) | ||
|
||
const maxDependabotUpdates = 220 |
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.
Is this a limitation of dependabot? I remember we hit a limit there sometime ago -- is this the one?
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.
That is the one. See this part of the diff for the Makefile changes calling 220: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/27269/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52L167
…metry#27269) **Description:** Change entirely how dependabot update entries are generated, by using the metadata.yaml status to find which components are most important in the distribution. The code now takes into account the distributions and the stability of the component as a score to decide whether to push the component. Go modules that don't have an associated metadata.yaml are not considered and therefore not present in the module updates path. **Link to tracking Issue:** open-telemetry#19410
Description:
Change entirely how dependabot update entries are generated, by using the metadata.yaml status to find which components are most important in the distribution.
The code now takes into account the distributions and the stability of the component as a score to decide whether to push the component. Go modules that don't have an associated metadata.yaml are not considered and therefore not present in the module updates path.
Link to tracking Issue:
#19410
Testing:
Tested by running
make gendependabot