invalid registries config in dependabot.yml

[yunnysunny]

Select Topic Area

Question

Body

I add a dependabot.yml in my project https://github.com/yunnysunny/session-token.

version: 2
registries:
  npm-mirror:
    type: npm-registry
    url: https://registry.npmmirror.com
updates:
  - package-ecosystem: "npm"
    directory: "/"
    registries:
      - npm-mirror
    schedule:
      interval: "weekly"

But it encountered an error:

The property '#/registries/npm-mirror/' of type object did not match one or more of the required schemas

https://github.com/yunnysunny/session-token/blob/master/.github/dependabot.yml

[lshigami]

The error you are getting is because the npm-mirror registry is not a supported registry by Dependabot. Dependabot only supports the following registries:

npmjs.com
yarnpkg.com
github.com//
If you want to use the npm-mirror registry, you will need to use a different tool to manage your dependencies.

Here is the updated dependabot.yml file that you can use:

version: 2
registries:
npmjs:
type: npm-registry
url: https://registry.npmjs.com
updates:

• package-ecosystem: "npm"
  directory: "/"
  schedule:
  interval: "weekly"
  This will configure Dependabot to check for updates to your dependencies on the npmjs.com registry on a weekly basis.

[yunnysunny]

The offical docs says we can use private registries: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#configuration-options-for-private-registries .
But why can't I use public registry since even private one is supported.

[Finn-Buhse]

I tried using the same as in your updated dependabot.yml file but the error persisted

[yunnysunny]

It encountered an error:

The property '#/updates/0/' contains additional properties ["registry-url"] outside of the schema when none are allowed

[yunnysunny]

registries.xxx.name is not a configuration option .

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬