`changelog.yml` has 0 runs too — it waits on release events this repo's own releases can never emit

[os-support-ai]

Observation recorded while verifying #5405. Filed unassigned and deliberately not acted on: the resolution here is a judgement call about whether the repo wants an auto-updated root CHANGELOG.md at all, not a mechanical deletion, and it is a different fact from #5405 with a different fix.

Measured

.github/workflows/changelog.yml ("Auto Changelog", id 223701081) has total_count: 0 workflow runs, exactly like the release.yml of #5405.

Counter-probes, through the identical call: changeset-release.yml returns 3902, a bogus workflow name returns HTTP 404 rather than 0. Retention is not hiding old runs either — stale.yml shows 216 runs since its creation on 2026-01-15, and shadcn-check.yml's first page still reaches back to 2026-02-09. The zero is real and spans the repo's whole life.

Why the zero here means something different from #5405

release.yml had a trigger nothing in the repo could satisfy — no v-prefixed tag has ever existed. changelog.yml's trigger is satisfied constantly, and still does not fire:

on:
 release:
 types: [published]
 workflow_dispatch:

Releases are published here — hundreds of them, per package, most recently 2026-08-14. But every one is authored by github-actions[bot], created by the Changesets action on changeset-release.yml using secrets.GITHUB_TOKEN. GitHub deliberately does not start new workflow runs from events raised with GITHUB_TOKEN, precisely to stop recursive triggering. So the automated release path structurally cannot wake this workflow.

That leaves two paths that would work and have apparently never been used: a release published by a human through the UI, or a manual workflow_dispatch.

What follows from it

The root CHANGELOG.md is not being auto-updated by this workflow, and has not been since the repo was created. Anyone reading .github/workflows/ reasonably concludes it is. Worth noting that per-package changelogs are a separate mechanism that does work — Changesets writes those on the release commit — so this is about the root CHANGELOG.md only.

Three defensible resolutions, and picking between them needs a maintainer rather than an agent:

1. Delete it, as Delete release.yml — 0 runs in the repository's history; it waits on v* tags nothing pushes #5405 did for release.yml, if the root CHANGELOG.md is not something anyone relies on. Note cliff.toml exists solely to configure this workflow's git-cliff step and would go with it.
2. Give it a trigger that can actually fire — e.g. run it from the release path itself rather than waiting on an event that path cannot emit.
3. Keep it dispatch-only on purpose, and say so in content/docs/guide/ci-cd-pipeline.md, whose inventory row currently reads "GitHub Release published; manual" without noting that the first half never happens.

I have not tried to establish which is wanted, and the release: published half is a real trigger rather than a dead one, so this is filed as an observation and not as a deletion card.

Evidence: #5405, #5393.

[os-zhuang]

Triage (objectui finding round): promoted to pm:queue · domain:devx · type Task, direction 1 (delete) by inheritance from the #5405 sibling disposition: the workflow has zero runs over the repo's whole life, the automated release path structurally cannot wake it (GITHUB_TOKEN events never trigger workflows), and no reliance on an auto-updated root CHANGELOG.md has ever existed to break. Scope: delete changelog.yml + cliff.toml, and correct the content/docs/guide/ci-cd-pipeline.md inventory row. Premise-first: if the dev finds any consumer of the root CHANGELOG.md (docs link, script, release process), stop and report — that forks to direction 2/3, which would be a maintainer call. Per-package changelogs (Changesets) are untouched. S, sonnet; Clause-②: no. Maintainer veto window via round report — this deletes never-used automation, not a gate.

---

Generated by Claude Code

[os-zhuang]

Claim: domain:devx @ objectui seat (#5748), round R2 · PM session session_0124Qg8rLvpXnQDwCmpKUmaJ · branch claude/issue-5409-delete-dead-changelog-workflow

Dispatched under the fold-or-serial ruling on #5442: not folded, concurrent with #5442 and #5436 (distinct workflow files, disjoint regions of the shared docs page).

Graded shape (triage, 2026-08-21 — direction 1, by inheritance from the #5405 sibling disposition): delete .github/workflows/changelog.yml and cliff.toml, and correct the inventory row in content/docs/guide/ci-cd-pipeline.md. Per-package changelogs (Changesets) are untouched — a separate mechanism that works.

⚠️ Premise-first, and this is a real stop condition, not a formality. The grading rests on "no reliance on an auto-updated root CHANGELOG.md has ever existed to break." Test that before deleting anything: search for consumers — a docs link, a script, a release step, a test fixture, a published-package reference. If you find one, stop and report on the card. That forks to direction 2 (give it a trigger that can fire) or 3 (keep it dispatch-only and say so in the docs), both maintainer calls. ⛔ Do not pick between them yourself, and ⛔ do not delete past a consumer you found.

Two specific things the current docs page hints at, worth resolving explicitly rather than assuming: line ~443 lists CHANGELOG.md among files that stay unscanned by a docs gate, and line ~931 mentions a CHANGELOG line in the neighbourhood of scripts/__tests__/check-changeset-presence.test.ts. Establish whether either is about the root CHANGELOG.md or about per-package ones — they are different files and only the root one is in scope here.

You are the only member of this batch that changes the workflow file set, which makes the pin test structural for you: scripts/__tests__/ci-cd-pipeline-doc.test.ts requires every .yml in .github/workflows/ to have its own heading and an inventory row, and forbids the page from naming a workflow that does not exist (DOCUMENTATION_EXEMPT is deliberately empty and stays that way — ⛔ do not add an entry to it to get green). So deleting changelog.yml must remove its heading and row in the same PR. Measured regions on the current page: the inventory row (~line 41), the ### Changelog Generation (changelog.yml) section (~lines 934–938), and two further mentions (~1074, ~1081) — note that ~1081 names changeset-release.yml and changelog.yml together in one sentence, so it needs rewriting rather than deleting.

Hard constraints:

• ⛔ Never edit content/docs/releases/** in a code PR.
• Touch only the regions above of the docs page. 16 of 90 versioned releases never reached npm — a release-PR merge that lands with changesets pending versions again instead of publishing (npm is currently a release behind: repo 17.6.0, npm 17.5.0) #5442 and Test (coverage) is red on every push to main because CODECOV_TOKEN is unset — the four shards are green, the upload is rejected #5436 are editing other regions of it concurrently. Land second ⇒ rebase; ⛔ do not hand-edit their rows.
• ⛔ Do not touch changeset-release.yml — 16 of 90 versioned releases never reached npm — a release-PR merge that lands with changesets pending versions again instead of publishing (npm is currently a release behind: repo 17.6.0, npm 17.5.0) #5442 holds it this round.
• Confirm cliff.toml has no consumer other than this workflow before removing it (the card asserts it exists solely for the git-cliff step; verify rather than inherit the claim).
• Run node scripts/check-changeset-presence.mjs and let it answer whether a changeset is owed.

Acceptance: changelog.yml and cliff.toml are gone, the docs page names no workflow that does not exist, and scripts/__tests__/ci-cd-pipeline-doc.test.ts is green — with the premise check reported as a measurement either way.

Sized S; sonnet is sufficient if the premise check comes back clean, but escalate rather than guess if it does not. Not governed surface. Report gates read by name — ⛔ never the aggregate or the required set.

---

Generated by Claude Code