feat: configure bots to manage dependency updates #223
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
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.
Situation
Our current setup allows bots to create pull requests (PRs) for updating released code dependencies, which we want to avoid. Additionally, both Dependabot and Renovate are set up for this task, creating redundant PRs for the same updates.
Task
Action
Testing
Verification will take place after merging to confirm the expected updates occur in the designated folders.
Results
Upon successful implementation, Renovate will update the appropriate folders without duplicate PRs and now manage previously excluded paths.
Notes
Internal Ticket: SDK-1573