ci(docs): publish versioned Fern docs on release#1541
Conversation
After publishing latest, also publish a version-tagged snapshot using `fern generate --docs --version "$RELEASE_TAG"`. RELEASE_TAG is already resolved at workflow scope (inputs.tag or github.ref_name, e.g. v0.0.47). Closes NVIDIA#1296
mesutoezdil
requested review from
a team,
derekwaynecarr,
maxamillion and
mrunalp
as code owners
|
Curious if we can keep the last N versions around, instead of all of them. Maybe the last 10. But users should be upgrading routinely as we are still in Alpha. For the instances where we have major breaking changes and paused releases a last N approach should suffice IMO. @drew was your original ticket intended to keep every version published indefinitely? |
Apologies for jumping in: the original ticket mentions "recent tagged releases" in the version selector, so a last-N cap aligns with the intent. I can add a max versions limit if you decide on a number |
2 participants
After each release,
fern generate --docspublishes tolatest.This PR adds a second call that also publishes a version-tagged snapshot so users on older installs can find docs that match their version.
Related Issue: Closes #1296
Testing
Workflow-only change. The
fern generate --docs --versionflag creates a new version entry on the Fern site using the tag as the slug. RequiresFERN_TOKENto verify end-to-end; the existingfern checkstep inbranch-docs.ymlvalidates the config locally.