Skip to content

Fix .github/dependabot.yml schema (set package-ecosystem to github-actions)#745

Open
Wayne-Ch wants to merge 1 commit into
mainfrom
Wayne-Ch/fix-dependabot-config
Open

Fix .github/dependabot.yml schema (set package-ecosystem to github-actions)#745
Wayne-Ch wants to merge 1 commit into
mainfrom
Wayne-Ch/fix-dependabot-config

Conversation

@Wayne-Ch
Copy link
Copy Markdown
Collaborator

Summary

Fixes the .github/dependabot.yml check that has been failing on every PR
opened since 5/27 (e.g. #727).

Root cause

The Dependabot config file added in commit 33a1a2f (Add Dependabot configuration file) contains an unfilled template — package-ecosystem is set to the empty string "", which fails Dependabot's schema validation:

The property '#/updates/0/package-ecosystem' value "" did not match
one of the following values: npm, bundler, composer, devcontainers,
dotnet-sdk, maven, mix, cargo, gradle, nuget, gomod, docker,
docker-compose, elm, gitsubmodule, github-actions, pip, terraform, pub,
rust-toolchain, sbt, swift, bun, uv, vcpkg, helm, conda, julia, bazel,
opentofu, pre-commit, nix, deno

The validation check is only run on pull requests, not on direct commits to main, so the broken template slipped in unnoticed and every new PR now hits a red .github/dependabot.yml check.

Change

Replace the empty package-ecosystem: "" placeholder with "github-actions". This:

  • Makes the file schema-valid → CI check passes on all future PRs.
  • Opts in only to GitHub Actions updates (low noise — the repo has 1 workflow file under .github/workflows/).
  • Leaves all other ecosystems unconfigured. Adding npm, pip, cargo, nuget, vcpkg, etc. is a separate decision that whoever owns those Dependabot update PRs should make in follow-up changes.

Diff

 version: 2
 updates:
-  - package-ecosystem: "" # See documentation for possible values
-    directory: "/" # Location of package manifests
+  - package-ecosystem: "github-actions"
+    directory: "/"
     schedule:
       interval: "weekly"

Scope

One file, two lines. Intentionally narrow — this is not an "enable Dependabot for the whole repo" PR. It is the minimum required to stop blocking unrelated PRs on a schema error.

The current config has an empty package-ecosystem field which fails
Dependabot's schema validation on every PR opened against the repo:

    The property '#/updates/0/package-ecosystem' value "" did not match
    one of the following values: npm, bundler, ..., github-actions, ...

Setting it to "github-actions" is the minimal change that makes the file
schema-valid while opting in to a low-noise ecosystem (only the workflow
files under .github/workflows/ are scanned). Additional ecosystems
(npm, pip, cargo, nuget, vcpkg, etc.) can be enabled in follow-up PRs
by whoever wants to own those Dependabot update PRs.
Copilot AI review requested due to automatic review settings May 29, 2026 22:12
@vercel
Copy link
Copy Markdown

vercel Bot commented May 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
foundry-local Ready Ready Preview, Comment May 29, 2026 10:13pm

Request Review

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes the Dependabot configuration schema error by replacing an empty package-ecosystem placeholder with the valid github-actions ecosystem.

Changes:

  • Enables Dependabot version updates for GitHub Actions workflows.
  • Keeps the existing weekly schedule and root directory configuration.

@natke natke self-requested a review May 29, 2026 22:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants