From 7cedd235b5978e0019d987f803aa1a9a9c8261c4 Mon Sep 17 00:00:00 2001 From: Prad Nukala Date: Fri, 25 Sep 2026 14:15:41 -0400 Subject: [PATCH] docs(cli): clarify changelog dating uses timever tag instead of API publish date --- apps/cli/release-topics.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/cli/release-topics.ts b/apps/cli/release-topics.ts index 304ea80..7a20de7 100755 --- a/apps/cli/release-topics.ts +++ b/apps/cli/release-topics.ts @@ -19,9 +19,9 @@ * The tag is annotated and backdated (tagger date = finish), so * `git tag --sort=taggerdate` reads as the campaign's history even for tags * minted by a backfill. The release's own published date cannot be backdated - * (the API has no field for it), and the docs changelog (githubReleases in - * apps/docs/blume.config.ts) dates entries by it — so a backfilled entry - * carries its real finish time in the version and the body's first sentence. + * (the API has no field for it), so the docs changelog dates each entry from + * this timever tag instead (`releasesDatedByTag` in apps/docs/blume.config.ts) + * — the tag format is that contract. * * Reconciles instead of reacting: every finished topic without a release gets * one, so a first run backfills the whole campaign; an existing release keeps