py/leetcode
1
0 Fork 0
mirror of https://github.com/prdlk/leetcode.git synced 2026-11-02 21:22:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(cli): clarify changelog dating uses timever tag instead of API publish date

Browse Source
This commit is contained in:
Prad Nukala committed 2026-09-25 14:15:41 -04:00
1 parent 107de04587
commit 7cedd235b5
1 file changed
+3 -3
Download Patch File Download Diff File Expand all files Collapse all files
apps/cli/release-topics.ts
+3 -3
View File
@@ -19,9 +19,9 @@
* The tag is annotated and backdated (tagger date = finish), so * The tag is annotated and backdated (tagger date = finish), so
* `git tag --sort=taggerdate` reads as the campaign's history even for tags * `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 * 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 * (the API has no field for it), so the docs changelog dates each entry from
* apps/docs/blume.config.ts) dates entries by it — so a backfilled entry * this timever tag instead (`releasesDatedByTag` in apps/docs/blume.config.ts)
* carries its real finish time in the version and the body's first sentence. * — the tag format is that contract.
* *
* Reconciles instead of reacting: every finished topic without a release gets * Reconciles instead of reacting: every finished topic without a release gets
* one, so a first run backfills the whole campaign; an existing release keeps * one, so a first run backfills the whole campaign; an existing release keeps