You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Close every actionable documentation gap introduced after NeMo Curator v1.2.0, and make the next release's docs/release notes complete enough for users to adopt new features and migrate breaking behavior.
Audit boundary and method
Primary boundary: commits reachable from main but absent from the v1.2.0 tag, reviewed through PR Add benchmark max timeout guard #2116 (merged 2026-06-29 19:34:32 UTC)
Original inventory: 67 PRs merged after the v1.2.0 publication timestamp
Supplemental code-freeze audit: 22 additional release-relevant PRs identified by Sara that merged after the 26.04 code freeze but before the release publication timestamp
Evidence reviewed: PR titles/bodies, changed file paths, git v1.2.0..main, and the current fern/versions/main/pages/ documentation tree
Decision rule: create focused docs work for user-facing features, public API/configuration changes, behavior changes, and migration hazards; bundle smaller release-note and reference gaps instead of creating noise
The publication timestamp alone was insufficient: it omitted release-relevant commits that missed v1.2.0 despite merging before the release was published. The supplemental disposition is tracked in #2144, #2145, and #2146.
These are smaller fixes, platform constraints, or already-partially-documented removals. They belong in the release/migration task rather than separate feature pages:
Goal
Close every actionable documentation gap introduced after NeMo Curator v1.2.0, and make the next release's docs/release notes complete enough for users to adopt new features and migrate breaking behavior.
Audit boundary and method
mainbut absent from the v1.2.0 tag, reviewed through PR Add benchmark max timeout guard #2116 (merged 2026-06-29 19:34:32 UTC)git v1.2.0..main, and the currentfern/versions/main/pages/documentation treePlanned documentation workstreams
Child issues are linked above for traceability.
Complete PR disposition
Dedicated docs workstreams required (18)
These PRs add or change user-facing workflows/APIs and need more than a release-note bullet:
#1727, #1835, #1863, #1898, #1899, #1980, #2033, #2036, #2038, #2045, #2054, #2058, #2062, #2070, #2072, #2077, #2086, #2110
Release-notes or migration coverage required (8)
These are smaller fixes, platform constraints, or already-partially-documented removals. They belong in the release/migration task rather than separate feature pages:
#2024, #2049, #2053, #2055, #2057, #2104, #2107, #2109
Documentation already landed; verify in release sweep (9)
No standalone follow-up is currently justified, but the release-notes owner should verify navigation, versioning, and consistency:
#1983, #1961, #1991, #2000, #2029, #2030, #2071, #2096, #2114
No public docs change required (32)
Dependency/security lockfile updates, CI/release plumbing, test-only changes, and internal benchmark-harness maintenance:
#1966, #2001, #2002, #2009, #2021, #2022, #2026, #2032, #2035, #2039, #2041, #2043, #2046, #2047, #2048, #2068, #2079, #2081, #2082, #2083, #2084, #2085, #2087, #2088, #2091, #2099, #2100, #2103, #2105, #2108, #2115, #2116
Supplemental code-freeze disposition
Sara's follow-up list added 22 release-relevant PRs that were outside the original publication-time query.
New dedicated or bundled workstreams
fit_data_fractionandcache_pathtoKMeansStage#1927Added to existing workstreams
MegatronTokenizerWriter#1427Bundled release-note coverage (#2144 and #2120)
#1746, #1762, #1763, #1774, #1870, #1880, #1888, #1890
Epic-level acceptance criteria
fern/versions/main/pages/about/release-notes/index.mdxdescribes 26.06 rather than 26.04task_idOut of scope