Dependabot’s private GitHub Packages access is back — now as fallback authentication

GitHub re-enabled automatic Dependabot authentication to private GitHub Packages and GitHub Container Registry dependencies on September 8, 2026 after temporarily rolling the feature back. GitHub's current editor note says the original release occurred June 23 and was withdrawn after a conflict caused some npm update jobs to resolve public packages through GitHub Packages. In the re-enabled implementation, Dependabot can still request `packages: read` on its short-lived `GITHUB_TOKEN` when a package grants the repository Manage Actions access, but automatic GitHub Packages credentials are now used only as fallback authentication. Explicit registry credentials and normal registry routing take precedence.

Private dependency automation often accumulates static credentials that have to be created, scoped, rotated and removed. Reusing repository-to-package access plus a short-lived job token still reduces that secret-management surface for teams whose private packages live on GitHub. The rollback also exposes an important dependency-management boundary: authentication convenience must not silently change registry selection. GitHub's fallback-only design is therefore more conservative than the original implementation and gives explicit package-routing configuration precedence.

GitHub initially shipped automatic GitHub Packages credentials for Dependabot on June 23, 2026, then temporarily rolled the feature back after some npm jobs resolved public dependencies through GitHub Packages. The September 8 release restores the feature with changed precedence behavior.

A package owner can grant the repository read access under Manage Actions access. Dependabot can then use its job `GITHUB_TOKEN` for qualifying GitHub Packages or `ghcr.io` pulls, but GitHub says this automatic credential is now fallback authentication. Explicit registry credentials and normal package-manager routing continue to take precedence.

When a GitHub-hosted private package is reachable through the repository grant and no separate credential is needed, teams can remove PAT-backed registry entries that existed solely for Dependabot. The corrected behavior does not change the core secret-reduction benefit.

Artifactory, Azure Artifacts, Nexus and other registries continue to use their own token, password or OIDC configuration. Private-network registries may also require self-hosted Dependabot runners or network allowlisting.