cp: docs: expand ATTRIBUTIONS.md to full 167-package inventory (2547) into r0.6.0 - #3092
Merged
Conversation
… into main (#2986) ## Summary - Cherry-pick of #2547 from `r0.5.1` into `main`. - Expands ATTRIBUTIONS.md from the manually curated subset to the full generated 167-package inventory (from the installed dependency graph / uv.lock). Signed-off-by: Kajal Jain <kajalj@nvidia.com> Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Kajal Jain <kajalj@nvidia.com>
This was referenced Sep 4, 2026
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>
Contributor
Author
|
/ok to test e913fb3 |
balasaajay
approved these changes
Sep 4, 2026
1 task
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
2 participants
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.
beep boop 🤖 (manual): the automated cherry-pick for #2986 into
r0.6.0did not fire — same root cause as #3091.Our PR title embedded the original r0.5.1 PR number (
(#2547)) ahead of GitHub's own squash-merge suffix ((#2986)). The automation's naiveawk -F'#' | awk -F')'parse grabbed the first match (2547, the closed original PR with no labels) instead of2986, found no target-branch label, and silently exited.This manually applies the same commit (
2cff3900onmain) that PR #2986 merged.