chore: remove npm from Dependabot — npm stays human-controlled#91
Merged
Conversation
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
1 participant
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.
npm version-updates are now human-controlled; package.json stays human-managed and Renovate deliberately does not manage npm on this repo.
The github-actions ecosystem was already migrated to Renovate (cutover #72), so npm was the last remaining Dependabot ecosystem. This deletes
.github/dependabot.ymlentirely, fully disabling Dependabot version-update PRs.Note: this does NOT touch Dependabot security alerts (a separate GitHub setting), which remain enabled.