Data & Analytics
dbt deps can fail after a Git redirect without a package change
Trace the client and credential path when private package installs start failing in CI.
November 17, 2026
When dbt deps starts failing in CI, the first suspect is often a changed token. A dbt issue describes a narrower failure: an Ubuntu 22.04 libcurl update changed behavior when a Git URL containing credentials redirects, producing “could not read Username” even though the package and Git version were unchanged. This is a useful diagnostic pattern, not a reason to expose the token in logs.
Reproduce the redirect safely
Record the dbt version, base image digest, libcurl package version and the normalized repository URL shape. Compare a failing job with the last working image in a controlled runner. Check whether the URL redirects, including a missing .git suffix, without printing the credential-bearing URL. dbt's package guide documents Git packages and secret environment variables; it also describes native private packages for supported setups.
Select the supported fix path
The dbt v1.11.17 release notes describe supplying credentials through a Git credential helper for redirecting repositories. Verify the installed patch level before spending time rotating a valid secret. If an upgrade is not immediately possible, test a canonical URL or an approved SSH/native-private-package path in staging, with security review for the credential handling. Avoid downgrading system security packages as a permanent fix.
Make CI failure informative
Keep a regression check for the private package install. Log the dbt, Git and libcurl versions and repository host, not credentials. A package install is a dependency of every downstream model build; it deserves a clear owner and rollback decision.
Adovo’s view
A failing dependency install is a supply-chain boundary, not a warehouse mystery. Find the changed layer before changing secrets. Reliable analytics begins before the first model runs.
