Add record_ecosystem_meta API support#407
Merged
jakecoffman merged 3 commits intodependabot:mainfrom May 7, 2025
Merged
Conversation
Contributor
Author
|
@kbukum1, @amazimbe, @abdulapopoola tagging for visibility as you were involved with the original change dependabot/dependabot-core#10905. |
JamieMagee
approved these changes
Mar 12, 2025
c0e79f5 to
f6788c3
Compare
f6788c3 to
8c7b98e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In dependabot/dependabot-core#10905, a new
record_ecosystem_metaAPI was added. This API is not implemented by dependabot-cli.When performing updates for an ecosystem that invokes the API (e.g. pip), the API server will throw 501 errors until updater retry limit is reached:
This API is called multiple times per dependency update and is compounded by the 3 retries per call. The volume of these errors causes the update process to take significantly longer than normal.
After this change, the API server returns 200 and the updater doesn't report error:
The output scenario file now contains the
record_ecosystem_metadata: