docs(fern): promote v1.3.1 to current release - #12752
Merged
Merged
Conversation
Move CURRENT_VERSION/DATE/TAG/WHEEL to v1.3.1 (wheel 1.3.1, no post suffix), add the v1.3.1 RELEASES entry as kind: patch pointing at the v1-3-0 notes page, and add the three 1.3.1 CUDA_HISTORY rows. Bump ARTIFACTS only for artifacts verified published at 1.3.1: all 10 containers (7 base + 3 -efa), the 3 PyPI wheels, and 8 crates. Left at 1.3.0: dynamo-protocols, dynamo-parsers and dynamo-config, which have no 1.3.1 on crates.io, and both Helm charts, whose publish state could not be confirmed. Regenerated the derived reference pages and feeds with docs/fern/scripts/gen_llms_tables.py. Signed-off-by: Dan Gil <dagil@nvidia.com>
github-actions
Bot
added
docs
documentation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (6)
WalkthroughThe release documentation now identifies Dynamo v1.3.1 as the current patch release. It adds CUDA compatibility data, updates applicable artifact references, records release notes, and publishes the release in the Atom feed. ChangesDynamo v1.3.1 release
Estimated code review effort: 3 (Moderate) | ~20 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Comment |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
![dynamo-review-agent[bot]](https://avatars.githubusercontent.com/u/201626793?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 737cd38a65
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Promoting a patch to CURRENT_VERSION surfaced several assumptions in the release-data consumers. Four fixes: - Correct the v1.3.1 delta text, which claimed backend pins were identical to v1.3.0 while recording nixlSglang 1.3.2 against 1.3.0. - Record a per-release wheel version. stableWheelCommand() previously substituted CURRENT_WHEEL only for the current release and otherwise assumed the wheel matched the container tag, so selecting v1.3.0 emitted ai-dynamo==1.3.0, which was never published; v1.3.0 shipped 1.3.0.post1. - Add a v1.3.1 section and #v131 anchor to the known-issues page and relabel v1.3.0. ReleaseHeader, UpgradePanel and TagLookup all build a known-issues#<anchor> link from the current version, so #v131 was a dead anchor in three components. - Add a Patch releases > v1.3.1 section to the v1-3-0 notes page, which the v1.3.1 notesHref points at, following the v1.2.1 precedent on the v1-2-0 page. Also narrows the v1.3.0 EFA known issue, which promised a v1.3.1 fix for GB200 and H100 / P5; v1.3.1 resolves GB200 only. Signed-off-by: Dan Gil <dagil@nvidia.com>
Contributor
Both were labelled 'Targeted fix: v1.3.1' but shipped no fix in that release. v1.3.1 carried one functional change (#12106, the EFA KV-transfer stall); the branch has no KVBM commit, and it still pins TensorRT-LLM 1.3.0rc19 while that issue's fix requires rc21. main is on rc23, so v1.4.0 is where both land. Signed-off-by: Dan Gil <dagil@nvidia.com>
sttts
reviewed
Aug 6, 2026
The v1.3.1 atom entry carried the same alternate link as v1.3.0, so two feed entries resolved to one page. Anchor the v1.3.1 section on the shared minor-line page and point notesHref at it. Earlier patch releases share this collision (v1.2.1, v1.1.1, v1.0.x all link to their parent page's top) because those pages carry no section anchors. Not retrofitted here. Signed-off-by: Dan Gil <dagil@nvidia.com>
sttts
approved these changes
Aug 6, 2026
hhzhang16
added a commit
that referenced
this pull request
Aug 6, 2026
dyn-3691-extract-shared-target-pid-cuda-customstorage-operation-layer * 'main' of https://github.com/ai-dynamo/dynamo: (65 commits) fix(frontend): emit SGLang stream role once (#12741) docs(fern): promote v1.3.1 to current release (#12752) fix(docs): remove duplicate unscoped community-rail CSS rules (#12615) feat(operator): migrate CRD storage to v1beta1 (#11904) fix: synchronize self-benchmark capacity across DP ranks (#12021) chore(deps): bump dynamo-tokenizers to 1.8.0 (#12707) fix(frontend): preserve split UTF-8 characters (#12688) docs: align Kubernetes build selector with CLI (#12729) fix(frontend): preserve completion backend error status (#12706) fix(operator): replace snapshot pods after GMS restart (#11286) refactor(media): rename installer module, drop --packages per review fix(media): harden installer against three pre-redesign review findings fix(media): verify installs in a fresh interpreter; teach --pip-args= form test(serve): install test-time decoders at the validated bounds feat(media): explicit installer for additional media decoders docs(spica): correct kv_load_ratio support guidance (#12714) feat(operator): add experimental grove.forceScalingGroup for single-node components (#11772) fix(vllm): declare entry-stage engine_input_source in GLM-Image NIXL config (#12709) chore: bump trtllm to v1.3.0rc23 (#12532) perf: remove trtllm postprocessing workers from the args as post processing workers are not effective in dynamo (#12592) ... Signed-off-by: Hannah Zhang <hannahz@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.
Overview
Promotes v1.3.1 to the current stable release in the Fern docs data file. Until this lands, the docs site renders v1.3.0 as current even though v1.3.1 is tagged, released, and published to NGC and PyPI.
What changed
docs/fern/components/releases.data.ts:CURRENT_VERSION/CURRENT_DATE/CURRENT_TAG/CURRENT_WHEELmoved to v1.3.1. The wheel is a plain1.3.1with no.postsuffix, unlike1.3.0.post1.RELEASESentry withkind: "patch", withnotesHrefpointing at the v1-3-0 notes page. Patch releases do not get their own page; this follows the v1.2.1 precedent.CUDA_HISTORYrows for 1.3.1. Toolkits are unchanged from 1.3.0 (13.0 for SGLang and vLLM, 13.1 for TensorRT-LLM).ARTIFACTSbumped for artifacts verified published at 1.3.1: 10 containers (7 base plus 3-efa), 3 PyPI wheels, 8 crates.Derived pages,
releases.json, and the atom feed regenerated withdocs/fern/scripts/gen_llms_tables.py.Deliberately left at 1.3.0
Each entry was checked against its registry rather than bumped by pattern:
dynamo-protocols,dynamo-parsersdynamo-configdynamo-platform,snapshotchartsBumping these would point the docs at artifacts that do not exist.
Pre-existing issues found, not fixed here
dynamo-confighas never published 1.3.0, so its artifact link on the live site is already dead. Out of scope for this change.dynamo-backend-commonpublished neither 1.3.0 nor 1.3.1.docs/fern/scripts/check_reference.shcheck 4 of 5 raisesStopIteration. Reproduced on a cleanmaincheckout, so it predates this branch.Verification
gen_llms_tables.pyreruns clean; every output reportsunchanged, so the committed twins match the data file.check_reference.sh: checks 1, 2, 3 and 5 pass, with 0 broken links inreference/. Check 4 fails identically on cleanmain.🤖 Generated with Claude Code
Summary by CodeRabbit