chore(deps): remove Dependabot version updates (PTC-96) - #179
Merged
Conversation
…C-96) Ungrouped weekly updates opened 8 PRs against main in a single day. Each one costs 8 ci.yml job runs (pytest x2, lint, secret-scan, build, docs, template-smoke x2), so eight one-line version bumps queued 64 job runs. They also targeted main, which CONTRIBUTING forbids -- nothing merges to main except a finished release branch. - target-branch: v0.1.11 so bumps land where work actually happens. Needs a one-line edit when the next release branch is cut. - Group into ci-actions / python-dev / python-runtime: 8 PRs becomes 2-3. - monthly instead of weekly, open-pull-requests-limit 2 per ecosystem. - Majors excluded from groups so they arrive as reviewable single PRs. - Ignore majors for dbt-core, dbt-duckdb, duckdb and dlt outright. These break in ways CI misses and users feel first; PTC-27 is the precedent, where an unreviewed Python bump took dbt out entirely. template-smoke is deliberately still run for bot PRs. It is the only gate that catches a runtime bump breaking project scaffolding. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Reverts the config rewrite in favour of deleting it. Two reasons the grouped-and-retargeted version does not work: - target-branch needs a manual edit every release cycle. It hardcodes the active release branch, so it silently rots the moment a new one is cut and starts aiming bumps at a shipped branch. - The docs are explicit that Dependabot will not use a config carrying target-branch for security updates: "you should not specify a target-branch". So the retargeting that fixes the workflow problem also breaks the one class of update actually worth having. What is lost: routine version bumps for SHA-pinned actions and Python deps. These were the entire problem -- weekly and ungrouped, they queued 8 PRs at 8 ci.yml job runs each. What is kept: vulnerability alerts stay on (verified enabled via the API), so CVEs still surface. They are configured in repo Settings, not here, and are unaffected by this deletion. There are currently 0 open alerts, which confirms all 8 open bot PRs were version noise, not security. Worth considering separately: repo Settings -> Advanced Security -> Dependabot security updates is currently disabled. Enabling it would give auto-PRs for CVEs only -- less noise than before and better coverage. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
db-tycoon-stephen
changed the title
This was referenced Jul 31, 2026
SECURITY.md claimed actions were 'updated via Dependabot', which stops being true once .github/dependabot.yml is removed. Replaces that with the release-time review, and states plainly that Dependabot *alerts* remain on so the vulnerability-disclosure path is unambiguous. Adds the review itself to CONTRIBUTING.md's release process, so removing the automation leaves a documented process behind rather than a gap. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Approving and merging. The ruff CI failure here is not from this PR — the import-ordering violations are pre-existing on |
JesuFemi-O
approved these changes
Aug 2, 2026
JesuFemi-O
left a comment
JesuFemi-O
left a comment
Contributor
There was a problem hiding this comment.
Config and docs only — no Python changes. Content is correct: Dependabot version-update PRs removed, security alerts preserved, CONTRIBUTING and SECURITY updated consistently. Ruff CI failure is pre-existing on main, not introduced here.
This was referenced Aug 2, 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
2 participants
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.
Deletes
.github/dependabot.yml. The config can't serve both the release-branch workflow and security updates —target-branchis what stops bumps aiming atmain, but the docs say not to set it if you want the config used for security updates, and it would need a manual edit every cycle regardless. Weekly ungrouped updates had queued 8 PRs (#161–#168, now closed) at ~64 CI job runs on a baseCONTRIBUTING.mdexcludes, with checks that weren't even reproducible — #168 failedruffonly because it ran three days later against an unpinneduvx ruff. #180 carries the four bumps worth taking againstv0.1.11;CONTRIBUTING.mdnow documents a dependency review at each release-branch cut, andSECURITY.mdno longer claims Dependabot updates the actions. Dependabot alerts stay enabled — they live in repo Settings, not this file.Two notes: CI is red on
rufffor reasons unrelated to this PR (mainruns unpinneduvx ruff check; #174 fixes it but targetsv0.1.11), andautomated-security-fixesis currently off — worth enabling before this lands.