Merged
Conversation
Member
|
How do we keep "update dependencies" PRs to an absolute minimum? I really really do not want to field an infinite series of "update deps" PRs until my death 😉 As part of the release seems OK, can we stick to that policy? |
Contributor
Author
|
I think that's fair. AWS SDK for example is released almost every day, we probably shouldn't update it every day. 😉 We could automate dependency updates using dependabot: it automatically updates dependencies in the form of PRs. One thing that would help reducing dependency updates is reducing dependencies. 🙂 Particularly the But until then, updating dependencies before releases is fine IMO. |
Signed-off-by: Mark Sagi-Kazar <mark.sagikazar@gmail.com>
sagikazarmark
force-pushed
the
update-dependencies
branch
from
a3ca83c to
a53b9db
Compare
peterbourgon
approved these changes
Jun 30, 2021
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
2 participants
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.
This PR updates some more dependencies (released since the last one or ones that I missed earlier) before the 0.11.0 release.