Greptile Summary

This PR removes the static latest-slug entry from fern/docs.yml and shifts to a purely position-based model where versions[0] (the semver-highest entry) is stamped "Latest · vX.Y.Z" at publish time. It also adds a sort -rV pass after each new-version insertion so backport patches (e.g. v0.3.1 arriving after v0.4.0) are placed correctly in the dropdown rather than appearing above newer releases.

• Removed dedicated latest entry (slug: latest) from fern/docs.yml; the stamp step now targets versions[0] by position instead of by slug, and the prune arithmetic is simplified (no more +1 offset).
• Added semver sort after each version insertion: slugs are extracted, sorted with sort -rV, the list is cleared, and entries are rebuilt in descending order.
• Stamp step cleaned up: gh api call replaced by a direct yq read of versions[0].display-name, though the now-unused GH_TOKEN env binding was left behind.

Confidence Score: 4/5

Safe to merge for normal forward-release workflows; the sort and stamp logic work correctly for the common case.

The core changes are mechanically sound. The sort-and-rebuild loop hard-codes display-name from the raw slug, silently discarding any future custom labels, and the GH_TOKEN env binding is dead code left over from the old gh api call. Neither affects current behaviour.

.github/workflows/publish-fern-docs.yml — the sort rebuild loop and the unused GH_TOKEN env warrant a second look.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Tag push / manual dispatch] --> B{is_release?}
    B -- false / pre-release --> G
    B -- true --> C{version file already exists?}
    C -- yes --> G
    C -- no --> D[Generate fern/versions/vX.Y.Z.yml from tag]
    D --> E[Append entry then sort -rV and rebuild list]
    E --> F[Prune oldest entries beyond MAX_VERSIONS]
    F --> G[Checkout frozen version content]
    G --> H[Stamp versions_0 as Latest vX.Y.Z]
    H --> I[fern generate docs - Publish]
    I --> J{is_release?}
    J -- false --> K[Done]
    J -- true --> L[Restore pre-stamp docs.yml]
    L --> M[Open PR to persist registry changes to main]

_{Reviews (3): Last reviewed commit: "fix(ci): frozen-only versioning — remove..." | Re-trigger Greptile}

🌿 Preview your docs: https://nvidia-preview-pull-request-338.docs.buildwithfern.com/topograph

Updated to frozen-only versioning — addresses the gap issue greptile flagged:

• Removed the live "Latest" entry pointing at docs/index.yml entirely
• All dropdown versions now serve frozen content from their git tag
• Every release is always registered (no skip-latest logic, no SHOULD_REGISTER)
• The newest entry is stamped "Latest · vX.Y.Z" at publish time (transient, not persisted)
• Prune counts versions directly (no +1 offset)

Simulated locally — v0.4.0 publish shows Latest · v0.4.0, v0.3.0. A subsequent v0.5.0 release correctly produces Latest · v0.5.0, v0.4.0, v0.3.0. No gaps, no duplicates.

Aligned with the NVSentinel frozen-versions branch (pdmack/NVSentinel@pdmack/fern-frozen-versions).

@greptileai