dependabot / dependabot/dependabot-core

Dependabot configured, but shows "Dependabot version updates aren't configured yet"

Open
#11,201 12 comments 0 reactions 1 assignee View on GitHub

@AbhishekBhaskar is already working on this.

Since Jan 6, 2026.

L: github:actions L: go:modules L: rust:cargo T: bug 🐞
Dominant language
Ruby
Stars
5.8k
Forks
1.5k
Avg merge
2d 18h
Merged PRs (30d)
149

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Package ecosystem

cargo, github-actions

### Package manager version

_No response_

### Language version

_No response_

### Manifest location and content before the Dependabot update

https://github.com/YaLTeR/niri/blob/main/Cargo.toml

https://github.com/YaLTeR/niri/blob/main/.github/workflows/ci.yml

### dependabot.yml content

https://github.com/YaLTeR/niri/blob/main/.github/dependabot.yml

### Updated dependency

_No response_

### What you expected to see, versus what you actually saw

I'm trying to configure Dependabot.

At first it checked for updates, but errored out for both Cargo and github_actions. The logs unfortunately got overwritten as I tried to re-run the workflows later, but for Cargo it errored because it failed to parse workspace from my subcrate Cargo.toml (seems some logic mismatch between dependabot and cargo itself), and for github_actions with some weird failed to resolve version error. It did successfully create PRs to update some Cargo packages though, which I later merged.

Since then, it stopped running any workflows or doing anything, even validating the dependabot.yml changes. The Insights panel shows "Dependabot version updates aren't configured yet".

Following #7357 and similar issues, I tried enabling/disabling security updates, and deleting and re-creating dependabot.yml from GitHub UI. Nothing helps, it keeps being stuck like this.

### Native package manager behavior

_No response_

### Images of the diff or a link to the PR, issue, or logs

_No response_

### Smallest manifest that reproduces the issue

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.