Describe the Bug
The nightly ledger on the Release Artifacts page reports a newest nightly build that is two weeks older than the newest nightly that exists, and older than what the install selector on a sibling page reports for the same day.
NIGHTLY_BUILDS in docs/fern/components/releases.data.ts — rendered by NightlyBuilds.tsx — is a hand-maintained literal. #13599 replaced the install selectors' nightly data with docs/fern/scripts/gen_nightly_selector.py, which resolves nightlies from the dated NGC tags at docs-publish time, but deliberately left this ledger alone. The ledger has drifted since.
Steps to Reproduce
- Open the Release Artifacts reference page and read the Nightly Builds table.
- Open the nightly channel of the install selector.
- Compare the newest nightly each one reports.
Expected Behavior
Both name the same newest nightly, because both describe the same set of published builds.
Actual Behavior
They disagree (as of filing):
NIGHTLY_BUILDS newest entry: 1.5.0.dev20260831 (Aug 31, 2026)- generated selector latest rows:
1.5.0.dev20260914 (Sep 14, 2026)
Nothing catches the drift. The Check component-rendered data has an agent-readable twin pre-commit hook passes either way — it checks that rendered data has a twin, not that the two nightly views agree. gen_llms_tables.py also reads NIGHTLY_BUILDS, so the stale dates propagate into the agent-readable tables and releases.json.
Environment
Published docs site; not environment-specific. Source at docs/fern/components/releases.data.ts.
Additional Context
Follow-up from review of #13599. Fix options, roughly in order of cost:
- Generate
NIGHTLY_BUILDS from the same NGC tag walk the selector already does, and drop the literal.
- Have
NightlyBuilds.tsx read the generated module directly and render the ledger from it.
- Add a check that fails when the ledger's newest entry predates the generated selector's latest row, leaving the ledger hand-maintained but no longer silently stale.
Either of the first two removes the hand-maintenance; the third only makes the drift visible.
Screenshots
No response
Describe the Bug
The nightly ledger on the Release Artifacts page reports a newest nightly build that is two weeks older than the newest nightly that exists, and older than what the install selector on a sibling page reports for the same day.
NIGHTLY_BUILDSindocs/fern/components/releases.data.ts— rendered byNightlyBuilds.tsx— is a hand-maintained literal. #13599 replaced the install selectors' nightly data withdocs/fern/scripts/gen_nightly_selector.py, which resolves nightlies from the dated NGC tags at docs-publish time, but deliberately left this ledger alone. The ledger has drifted since.Steps to Reproduce
Expected Behavior
Both name the same newest nightly, because both describe the same set of published builds.
Actual Behavior
They disagree (as of filing):
NIGHTLY_BUILDSnewest entry:1.5.0.dev20260831(Aug 31, 2026)1.5.0.dev20260914(Sep 14, 2026)Nothing catches the drift. The
Check component-rendered data has an agent-readable twinpre-commit hook passes either way — it checks that rendered data has a twin, not that the two nightly views agree.gen_llms_tables.pyalso readsNIGHTLY_BUILDS, so the stale dates propagate into the agent-readable tables andreleases.json.Environment
Published docs site; not environment-specific. Source at
docs/fern/components/releases.data.ts.Additional Context
Follow-up from review of #13599. Fix options, roughly in order of cost:
NIGHTLY_BUILDSfrom the same NGC tag walk the selector already does, and drop the literal.NightlyBuilds.tsxread the generated module directly and render the ledger from it.Either of the first two removes the hand-maintenance; the third only makes the drift visible.
Screenshots
No response