Limit Dependabot Go module updates to security advisories only - #70914
Merged
potiuk merged 1 commit intoAug 3, 2026
Conversation
The Go SDK's dependencies resolve directly to upstream repositories. Unlike PyPI or npm, there is no central registry that pre-scans a release before it is published, and whoever controls a module's namespace can cut a release at any time. A dangling/hijacked namespace (as recently seen with slogcolor) could therefore land a malicious version through a routine Dependabot bump into contributors' dev environments and CI before anyone reviews it. Disable automatic version-update PRs for the go-sdk gomod ecosystem on the default branch (open-pull-requests-limit: 0) and keep only advisory-driven security updates, which require a published GHSA advisory and cannot be triggered by an upstream release self-declaring itself a security fix. Routine Go dependency bumps are now done manually when needed. Raise the gomod cooldown to 14 days so any release that is auto-considered on the v3-3-test branch has a longer window to be flagged before it is pulled in.
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-3-test
1 task
potiuk
approved these changes
Aug 3, 2026
Contributor
Backport failed to create: v3-3-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker eb076fe v3-3-testThis should apply the commit to the v3-3-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
This was referenced Aug 6, 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.
Why
The Go SDK's dependencies resolve directly to upstream repositories. Unlike PyPI or npm, there is no central registry that pre-scans a release before it is published, and whoever controls a module's namespace can cut a release at any time.
Go's checksum database (
go.sum+sum.golang.org) makes existing pins immutable, so the risk is not the current pin — it is the next automatic bump.What
For the
gomodecosystem rooted at/go-sdk:open-pull-requests-limit: 0) and keep only the advisory-drivengo-sdk-security-updatesgroup. Dependabot security updates require a published GHSA advisory, so they cannot be triggered by an upstream release self-declaring itself a "security" fix. Routine Go dependency bumps are now done manually when we actually need them.v3-3-testbranch still does grouped minor/patch bumps).This only changes the automation posture for Go modules — no dependency versions change, and security fixes still flow automatically.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines