chore: remove Dependabot in favor of the weekly batch dependency update [RED-695] [ship]#1395
Merged
Merged
Conversation
…[RED-695] Dependabot opened up to 3 npm version-update PRs daily, duplicating the weekly batched dependency update that is Node-floor aware and respects the minimumReleaseAge embargo in pnpm-workspace.yaml. Its output was already being discarded: the five most recent Dependabot PRs were closed rather than merged. Dependabot's version updates were the only remaining producer of the `dependencies` label, so the `Improvements` category that mapped it in .github/release.yml is removed too, along with the `dependencies` exclusion under `Other Changes`. Weekly batch PRs are unlabeled and already fall into `Other Changes`, so generated release notes are unaffected in practice. Dependabot security alerts and security updates are a repository setting rather than a function of this config and remain enabled. Should a security-update PR be opened and merged, it carries the `dependencies` label and is now grouped under `Other Changes`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
sorccu
changed the title
sorccu
changed the title
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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.
Linear: RED-695
Dependabot opened up to 3 npm version-update PRs daily, duplicating the weekly batched dependency update that is Node-floor aware and respects the
minimumReleaseAgeembargo inpnpm-workspace.yaml. Its output was already being discarded — the five most recent Dependabot PRs (#1375, #1376, #1379, #1380, #1381) were closed rather than merged.This deletes
.github/dependabot.yml, leaving the weekly batch as the single dependency-update path.Why
.github/release.ymlchanges tooDependabot applied a
dependencieslabel, and.github/release.ymlmapped that label to a dedicatedImprovementssection in GitHub's auto-generated release notes. Dependabot's version updates were that label's only producer, so the category is removed along with thedependenciesexclusion underOther Changes.Generated release notes are unaffected in practice: the weekly batch PRs are unlabeled and already fall into
Other Changes.Scope
Dependabot has no other footprint — no workflow gates on
dependabot[bot], nodependabot/**branch filters, nosecrets.DEPENDABOT_*, no auto-merge workflow, and no docs referencing it. No Dependabot PRs are currently open, so none are orphaned. GitHub stops scheduling version updates once the config is absent from the default branch, i.e. on merge.Out of scope
Dependabot security alerts and security updates are a repository setting rather than a function of this config, and intentionally remain enabled so security patches keep flowing outside the weekly cadence. Note that Dependabot labels every PR it opens
dependencies, security-update PRs included — should one be merged, it now groups underOther Changesinstead of the removedImprovementssection. That grouping change is cosmetic.