refactor(cli): generate docs/site.json manifest and update docs site references

This commit is contained in:
Prad Nukala committed 2026-10-05 13:51:14 -04:00
1 parent 0b004fcba2
commit e9d40020f4
3 files changed
+82 -137

No files matched your search

+4 -4
View File
@@ -21,14 +21,14 @@
* tagged commit — the last main commit before the finish. Problems still open
* at the finish are left out: the release records what finished, and an open
* optional problem is tracked by its issue (or its Review day), not here.
* apps/docs/lib/releases.ts reads these `### Closed …` tables back for the
* docs `/changelog` timeline, so their row shape is its contract.
* The docs site (prdlk/cs `lib/releases.ts`) reads these `### Closed …`
* tables back for its `/changelog` timeline, so their row shape is its contract.
*
* 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), so the docs changelog dates each entry from
* this timever tag instead (apps/docs/lib/releases.ts)
* this timever tag instead (prdlk/cs `lib/releases.ts`)
* — the tag format is that contract.
*
* Reconciles instead of reacting: every finished topic or review without a
@@ -59,7 +59,7 @@ const DRY =
process.env.DRY_RUN === "1" ||
process.env.DRY_RUN === "true";
/** The docs site (apps/docs/blume.config.ts `deployment.site`); sync publishes `/<num>` short links. */
/** The docs site (prdlk/cs `blume.config.ts` `deployment.site`); it publishes sync's `/<num>` short links. */
const DOCS_SITE = "https://lc.prd.lk";
const TIMEVER = "https://gist.github.com/twolfson/de1b004dd22536b8e668";