docs: Clarify statement about dependencyDashboardApproval usage#35683
Merged
rarkins merged 1 commit intoMay 2, 2025
Merged
Conversation
d887db8 to
7b0d5c2
Compare
rarkins
approved these changes
May 2, 2025
|
🎉 This PR is included in version 40.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes
This PR adds a teeny tiny documentation improvement clarifying that setting dependencyDashboardApproval to true means that a particular upgrade requires approval also in the scenario where it's applied globally to a renovate configuration.
Context
The documentation was misleading about the meaning of dependencyDashboardApproval when used globally.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: