From bfcfd53de880ba9f7291d5020d5613679e923f81 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 8 Sep 2026 05:26:35 +0000 Subject: [PATCH] ci: drop the two dependabot labels this repo does not have `.github/dependabot.yml` requested `automated` (npm block) and `github-actions` (GitHub-Actions block). Neither is declared in `.github/labels.yml` nor exists in the repository, so Dependabot failed the labelling step on every PR it opened since 2026-08-10. The bot reports only that *a* label failed, never which one, so the second missing name was invisible from the notice alone; each referenced name was checked against the repo's actual label set. `dependencies` and `skip-changeset` were confirmed to exist and are kept. Dropped rather than created: `dependencies` already marks these PRs, and `.github/labels.yml` governs the taxonomy by design. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_019YKN9TPqDSSXUaYqp2j7MZ --- .../dependabot-labels-that-do-not-exist.md | 30 +++++++++++++++++++ .github/dependabot.yml | 2 -- 2 files changed, 30 insertions(+), 2 deletions(-) create mode 100644 .changeset/dependabot-labels-that-do-not-exist.md diff --git a/.changeset/dependabot-labels-that-do-not-exist.md b/.changeset/dependabot-labels-that-do-not-exist.md new file mode 100644 index 000000000..a422d25e0 --- /dev/null +++ b/.changeset/dependabot-labels-that-do-not-exist.md @@ -0,0 +1,30 @@ +--- +--- + +CI configuration only — this PR ships nothing to HotCRM users, so the +frontmatter above is deliberately empty (the sanctioned "releases nothing" +declaration that `.github/workflows/changeset-check.yml` documents, on par with +the `skip-changeset` label). No `src/` metadata changed: no object, field, view, +label, or hook handler logic. + +`.github/dependabot.yml` asked for two labels this repository does not have. +The npm block requested `automated` and the GitHub-Actions block requested +`github-actions`; neither is declared in `.github/labels.yml` — "the single +source of truth for this repository's labels" — and neither exists in the repo. +Dependabot cannot create labels, so it failed the whole labelling step and said +so in its first comment on every PR it opened, from #1058 (2026-08-10) onward. + +The reason this survived a month is that the failure was **unfalsifiable from +Dependabot's own error message**: the bot reports that *a* label could not be +applied, never *which* one. Deleting `automated` alone — the single name the +filed issue named — would have left the notice repeating with nothing new to +read, and no way to tell whether the fix had worked. Establishing that +`github-actions` was also missing required checking each referenced name against +the repository's actual label set, not reading the notice more carefully. + +Both names are dropped rather than created. `dependencies` already marks these +PRs and is enough to filter them, and `.github/labels.yml` governs the taxonomy +by design ("no ad-hoc labels"), so the config is brought to the manifest rather +than the manifest widened to the config. Both blocks now request only +`dependencies` and `skip-changeset`, which do exist, so Dependabot's labelling +step succeeds and its PRs become filterable. diff --git a/.github/dependabot.yml b/.github/dependabot.yml index e8d960703..992d56072 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -14,7 +14,6 @@ updates: # `@objectstack/*` upgrade, say), drop the label and add a changeset by hand. labels: - "dependencies" - - "automated" - "skip-changeset" commit-message: prefix: "chore" @@ -28,7 +27,6 @@ updates: interval: "monthly" labels: - "dependencies" - - "github-actions" - "skip-changeset" commit-message: prefix: "ci"