feat: Bypass Docker Hub rate limits, by prioritize docker updates #73
Conversation
This file contains 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
github-actions bot
pushed a commit
that referenced
this pull request
Jun 9, 2023
# [2.2.0](v2.1.1...v2.2.0) (2023-06-09) ### Features * Bypass Docker Hub rate limits, by prioritize docker updates ([#73](#73)) ([474c1bd](474c1bd))
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.
Put an
xinto the box if that applies:Description of your changes
Docker API rate limits prevent the creation PRs of any kind of updates, which can block update flow for the whole repo for hours if any docker-related update is available.
To avoid this, we simply update all Docker-specific updates on Monday, and process all other updates (including Docker updates too) on Tuesday.
How was it tested
During a few months in our infra repo.
How I can see from our huge infra repo with about ~15 docker-related deps, mainly located in the
regexmanager with a few deps from thedockermanager, that construction works pretty nice