Repository navigation
chore: remove dead dependabot ignore entries - #1237
Merged
Merged
Conversation
Every entry in the `ignore:` block was a no-op. Dependabot `ignore` entries that carry an explicit `versions:` list only suppress those exact versions, and all of the pinned versions now sit far below what the repo depends on, so none of them can match again. Three of them name packages the project no longer has at all -- `eslint`, `eslint-config-prettier` and `prettier`, all replaced by Biome. The other seven pin versions that every current range has long since passed: pod-install 0.1.x (now 1.0.6), release-it 14.x (now 18.x), @types/react-native 0.63-0.64 (now 0.73.0), react-native 0.64.0 (now 0.81.x), react 17.0.1 (now 19.1.0), typescript 4.x (now 5.9.3) and @types/react 17.0.0 (now 19.x). Removing a no-op cannot change which updates dependabot proposes, so this is behaviour-preserving. The remaining keys are untouched. Closes #1236 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Nov 15, 2026
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
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.
Closes #1236
What
Deletes the
ignore:block from.github/dependabot.yml. Nothing else in the file changes — the diff is 44 deletions and zero additions.Why this is safe
Dependabot
ignoreentries that carry an explicitversions:list suppress only those exact versions. Every pinned version is now far below what the repo actually depends on, so none can ever match again. Removing a no-op cannot change which updates dependabot proposes.package.jsoneslinteslint-config-prettierprettierpod-install1.0.6release-it^18.1.1@types/react-native0.73.0react-native^0.81.1react19.1.0typescript5.9.3@types/react^19.1.12The three ESLint/Prettier entries are the clearest case:
grep -iE "eslint|prettier" package.jsonreturns nothing and there are no ESLint or Prettier config files at the repo root, so those entries reference tooling that was removed when the repo moved to Biome.Verification
.github/dependabot.ymlis now exactly:I checked the resulting file is still valid YAML with
version,package-ecosystem,directory,schedule.intervalandopen-pull-requests-limitall unchanged, and thatignoreis gone.Note that CI does not validate
dependabot.yml, so the Build checks passing here says nothing about this file specifically — GitHub parses it on push to the default branch, and surfaces problems in the repo's Insights → Dependency graph → Dependabot tab. Worth a glance there after merge.🤖 Generated with Claude Code