dependabot / dependabot/dependabot-core

Ignore not working for private package

Open
#13,477 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

L: dotnet:nuget 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?
  • I have searched the existing issues
Package ecosystem

nuget

Package manager version

No response

Language version

dotnet 9.0

Manifest location and content before the Dependabot update

No response

dependabot.yml content
version: 2
updates:
  # Monitor NuGet packages
  - package-ecosystem: "nuget"
    directory: "/Source"
    schedule:
      interval: "weekly"
      day: "tuesday"
      time: "08:00"
      timezone: "America/New_York"
    open-pull-requests-limit: 10
    assignees:
      - "anyveldtpasen"
    labels:
      - "dependencies"
    ignore:
      - dependency-name: "OurOrg.CommonServices"
      - dependency-name: "Telerik.*"
    groups:
      minor-and-patch:
        update-types:
          - "minor"
          - "patch"
    commit-message:
      prefix: "chore"
      include: "scope"
Updated dependency

No response

What you expected to see, versus what you actually saw

I expected it to ignore the ignored packages. We want PRs for the nuget packages. Not our private package or the Telerik packages.

There are a number of packages that need updates in nuget, but this action failed as soon as it hit out private package and stopped.

updater | 2025/11/04 13:09:47 ERROR Error type: dependency_not_found

  • source: OurOrg.CommonServices
    proxy | 2025/11/04 13:09:47 [608] POST /update_jobs/1143319388/record_update_job_error
    proxy | 2025/11/04 13:09:47 [608] 204 /update_jobs/1143319388/record_update_job_error

I apologize if I am missing something in the config of this, but it seems like a bug for me. This is the first time I've tried this with ignore.

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.

Research direction

Start with the NuGet update path and the supplied dependabot.yml, especially the ignore entries for OurOrg.CommonServices and Telerik.*; compare that configuration with the dependency_not_found log. Done means an ignored private package no longer stops the update job and updates for other NuGet packages still proceed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.