docs(fern): add v0.5.1 version snapshot for GA release - #2731
Merged
Conversation
- Snapshots fern/versions/latest/ -> fern/versions/v0.5.1/ (97 files) to freeze the docs at the 0.5.1 GA state - Creates fern/versions/v0.5.1.yml with nav config pointing to the frozen pages - Registers v0.5.1 as stable in fern/docs.yml (between Main and 0.5.0) - Adds v0.5.1 release notes accordion to release-notes.mdx in both latest/ and the snapshot - Extends test_fern_docs_links.py version coverage to include v0.5.1 nemo_gym/package_info.py already reports 0.5.1 with no PRE_RELEASE suffix; no code changes needed there. Follows the same pattern as the v0.5.0 snapshot (#2389). Signed-off-by: Kajal Jain <kajalj@nvidia.com>
Contributor
Contributor
Author
|
/ok to test 4cbf1d9 |
2 tasks
kajalj22
added a commit
that referenced
this pull request
Sep 2, 2026
## Summary - Snapshots `fern/versions/latest/` → `fern/versions/v0.5.1/` (97 files) to freeze the docs at the 0.5.1 GA state - Creates `fern/versions/v0.5.1.yml` with nav config pointing to the frozen pages - Registers `v0.5.1` as `stable` in `fern/docs.yml` (between Main and 0.5.0) - Adds a v0.5.1 release notes accordion to `release-notes.mdx` in both `latest/` and the snapshot - Extends `test_fern_docs_links.py` version coverage to include `v0.5.1` Follows the same pattern as the v0.5.0 snapshot (#2389). Targeted directly at `r0.5.1` rather than `main` + cherry-pick, per direction on this release. `nemo_gym/package_info.py` already reports `0.5.1` with no `PRE_RELEASE` suffix, and `pyproject.toml` derives its version from it dynamically — no code version changes needed. ## Test plan - [x] `pytest tests/unit_tests/test_fern_docs_links.py -q` — 13 passed, 20 subtests passed - [x] Verify `docs.nvidia.com/nemo/gym` shows `0.5.1` in the version picker as stable - [x] Verify the v0.5.1 docs snapshot renders correctly at `/v0.5.1/` - [x] Verify release notes page shows the v0.5.1 accordion open by default, v0.5.0 collapsed Signed-off-by: Kajal Jain <kajalj@nvidia.com>
kajalj22
added a commit
that referenced
this pull request
Sep 4, 2026
- Snapshots `fern/versions/latest/` → `fern/versions/v0.5.1/` (97 files) to freeze the docs at the 0.5.1 GA state - Creates `fern/versions/v0.5.1.yml` with nav config pointing to the frozen pages - Registers `v0.5.1` as `stable` in `fern/docs.yml` (between Main and 0.5.0) - Adds a v0.5.1 release notes accordion to `release-notes.mdx` in both `latest/` and the snapshot - Extends `test_fern_docs_links.py` version coverage to include `v0.5.1` Follows the same pattern as the v0.5.0 snapshot (#2389). Targeted directly at `r0.5.1` rather than `main` + cherry-pick, per direction on this release. `nemo_gym/package_info.py` already reports `0.5.1` with no `PRE_RELEASE` suffix, and `pyproject.toml` derives its version from it dynamically — no code version changes needed. - [x] `pytest tests/unit_tests/test_fern_docs_links.py -q` — 13 passed, 20 subtests passed - [x] Verify `docs.nvidia.com/nemo/gym` shows `0.5.1` in the version picker as stable - [x] Verify the v0.5.1 docs snapshot renders correctly at `/v0.5.1/` - [x] Verify release notes page shows the v0.5.1 accordion open by default, v0.5.0 collapsed Signed-off-by: Kajal Jain <kajalj@nvidia.com>
kajalj22
added a commit
that referenced
this pull request
Sep 4, 2026
…2987) ## Summary - Cherry-pick of #2731 from `r0.5.1` into `main`. **Stack position 4 of 5** — #2547, #2629, #2725 (positions 1-3) merged as #2986, #2985, #2984. This is now next in line, rebased directly onto `main`. - Adds the frozen `fern/versions/v0.5.1/` docs snapshot (and `fern/versions/v0.5.1.yml`) for the v0.5.1 GA release, mirroring how prior GA versions (v0.5.0, v0.4.0, ...) got their own version snapshot in the docs site. - Also inserts the v0.5.1 accordion into `release-notes.mdx`, between the newer v0.6.0 entry (already on `main`) and v0.5.0. - Note on PR title: intentionally omits `(#2731)` — the release-branch auto-cherrypick automation (`cherry-pick-release-commit.yml`) naively grabs the *first* `(#NNNN)` in the squash-merge commit subject to resolve "which PR is this". Embedding the original PR number in the title broke that lookup for #2984/#2985/#2986 (see #3091/#3092 for the manual r0.6.0 backfills). Keeping this title number-free lets the automation resolve the real PR (#2987) and auto-create the r0.6.0 cherry-pick. Remaining stack (merge in this order): #2987 → #2983 ## Test plan - [ ] Confirm fern docs build picks up the new v0.5.1 version and the version switcher shows it - [ ] `tests/unit_tests/test_fern_docs_links.py` passes Signed-off-by: Kajal Jain <kajalj@nvidia.com>
jkyi-nvidia
pushed a commit
that referenced
this pull request
Sep 11, 2026
…2987) ## Summary - Cherry-pick of #2731 from `r0.5.1` into `main`. **Stack position 4 of 5** — #2547, #2629, #2725 (positions 1-3) merged as #2986, #2985, #2984. This is now next in line, rebased directly onto `main`. - Adds the frozen `fern/versions/v0.5.1/` docs snapshot (and `fern/versions/v0.5.1.yml`) for the v0.5.1 GA release, mirroring how prior GA versions (v0.5.0, v0.4.0, ...) got their own version snapshot in the docs site. - Also inserts the v0.5.1 accordion into `release-notes.mdx`, between the newer v0.6.0 entry (already on `main`) and v0.5.0. - Note on PR title: intentionally omits `(#2731)` — the release-branch auto-cherrypick automation (`cherry-pick-release-commit.yml`) naively grabs the *first* `(#NNNN)` in the squash-merge commit subject to resolve "which PR is this". Embedding the original PR number in the title broke that lookup for #2984/#2985/#2986 (see #3091/#3092 for the manual r0.6.0 backfills). Keeping this title number-free lets the automation resolve the real PR (#2987) and auto-create the r0.6.0 cherry-pick. Remaining stack (merge in this order): #2987 → #2983 ## Test plan - [ ] Confirm fern docs build picks up the new v0.5.1 version and the version switcher shows it - [ ] `tests/unit_tests/test_fern_docs_links.py` passes Signed-off-by: Kajal Jain <kajalj@nvidia.com> Signed-off-by: Junkeun Yi <jkyi@nvidia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fern/versions/latest/→fern/versions/v0.5.1/(97 files) to freeze the docs at the 0.5.1 GA statefern/versions/v0.5.1.ymlwith nav config pointing to the frozen pagesv0.5.1asstableinfern/docs.yml(between Main and 0.5.0)release-notes.mdxin bothlatest/and the snapshottest_fern_docs_links.pyversion coverage to includev0.5.1Follows the same pattern as the v0.5.0 snapshot (#2389). Targeted directly at
r0.5.1rather thanmain+ cherry-pick, per direction on this release.nemo_gym/package_info.pyalready reports0.5.1with noPRE_RELEASEsuffix, andpyproject.tomlderives its version from it dynamically — no code version changes needed.Test plan
pytest tests/unit_tests/test_fern_docs_links.py -q— 13 passed, 20 subtests passeddocs.nvidia.com/nemo/gymshows0.5.1in the version picker as stable/v0.5.1/