NVIDIA-NeMo / NVIDIA-NeMo/Curator
[Docs] Integrate 26.07 documentation PRs and stage the version train
Open
@lbliii is already working on this.
Since Jul 2, 2026.
documentation
needs-follow-up
r1.3.0
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 327
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 30
Description
Parent tracker: NVIDIA-NeMo/Curator#2118
Goal
Integrate the 26.07 documentation PR set without losing content at cross-PR merge boundaries, then stage the version train for publication.
Why this is required
An adversarial combined-tree merge found four real content-conflict groups even though the individual PRs pass validation:
- NVIDIA-NeMo/Curator#2135 and #2136 both add cards to the audio overview and tutorial index.
- NVIDIA-NeMo/Curator#2134 and NVIDIA-NeMo/Curator#2142 both extend the
ProcessingStageAPI reference. - #2130 and #2149 both extend the semantic deduplication page at the same insertion point.
- NVIDIA-NeMo/Curator#2143 and NVIDIA-NeMo/Curator#2147 both update the release-notes page. NVIDIA-NeMo/Curator#2143 is the canonical 26.07 rollup and must preserve the typed InferenceServer/Dynamo material.
Timing
Release blocker. Perform the reconciliation after the detailed feature PRs merge, but before NVIDIA-NeMo/Curator#2143 merges and before any docs/v1.3.0 publication tag is pushed.
Acceptance criteria
- Merge or rebase the audio pair and preserve both tutorial cards on both landing pages.
- Merge or rebase the resumability/worker-sizing pair and preserve both task-lineage and backend-configuration sections.
- Merge or rebase the deduplication pair and preserve both input-discovery and K-means fitting guidance.
- Merge NVIDIA-NeMo/Curator#2147 before NVIDIA-NeMo/Curator#2143, then rebase NVIDIA-NeMo/Curator#2143 and preserve the complete 26.07 release narrative.
- Run
fern check,git diff --check, and the generated-reference broken-link job against the combined tree. - Stage
v26.07, updatefern/docs.yml, redirects, and thelatest.ymlsymlink according to the version ship checklist. - Do not push the production
docs/v*tag until release authorization is explicit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.