ai-dynamo · dagil-nvidia · Aug 1, 2026 · Jul 27, 2026 · Jul 27, 2026 · Jul 27, 2026
@@ -1808,6 +1808,26 @@
       "firstTimers": 34,
       "breaking": 41,
       "knownIssues": 14
+    },
+    "v0.9.0": {
+      "firstTimers": 14,
+      "breaking": 1,
+      "knownIssues": 13
+    },
+    "v0.8.0": {
+      "firstTimers": 20,
+      "breaking": 0,
+      "knownIssues": 14
+    },
+    "v0.7.0": {
+      "firstTimers": 2,
+      "breaking": 0,
+      "knownIssues": 7
+    },
+    "v0.6.0": {
+      "firstTimers": 4,
+      "breaking": 0,
+      "knownIssues": 3
     }
   },
   "nightliesNote": "ai-dynamo and ai-dynamo-runtime nightly builds from main publish wheels tagged *.devYYYYMMDD (since Apr 24, 2026). Install with pip or uv using --pre and the NVIDIA extra-index pattern shown above."

@@ -6,8 +6,9 @@
  *
  * Answers "I run v1.1.x — what must I read to get to the current release?".
  * Self-configuring from releases.data: the target is CURRENT_VERSION and the
- * from-candidates are every older stable release that has a RELEASE_STATS
- * entry, labeled by line ("v1.2.x"). Each line maps to its LATEST release
+ * from-candidates are every older stable release that has both a RELEASE_STATS
+ * entry and a docs-native notes page, labeled by line ("v1.2.x"). Each line
+ * maps to its LATEST release
  * including patches (v1.2.x -> v1.2.1) so the migration strip reflects the
  * pins the user actually runs. Each panel reuses UpgradePanel's internals
  * (buildRows + MigrationStrip + ReadingListFooter + UpgradePanelStyles); the
@@ -104,10 +105,18 @@ function buildFromLines(): FromLine[] {
   const currentIdx = RELEASES.findIndex((r) => r.version === CURRENT_VERSION);
   if (currentIdx < 0) return [];
 
-  /* All stable releases carrying RELEASE_STATS, in RELEASES (newest-first)
-     order, with their array index for older/newer comparisons. */
+  /* Stable releases carrying RELEASE_STATS *and* a docs-native notes page, in
+     RELEASES (newest-first) order, with their array index for older/newer
+     comparisons. notesHref is the gate because the reading-list chips deep-link
+     to per-release sections on the Deprecations and Known Issues pages, which
+     exist only for releases that have a notes page. RELEASE_STATS on its own
+     also covers pre-v1.0.0 releases, which are counted on Release History but
+     have no such sections to point at. */
   const statStables = RELEASES.map((release, index) => ({ release, index })).filter(
-    ({ release }) => release.kind === "stable" && RELEASE_STATS[release.version] !== undefined,
+    ({ release }) =>
+      release.kind === "stable" &&
+      release.notesHref !== undefined &&
+      RELEASE_STATS[release.version] !== undefined,
   );
 
   return statStables

@@ -1020,11 +1020,42 @@ export interface ReleaseStats {
   knownIssues: number;
 }
 
+/* COUNTING RULES — apply these when ingesting a new release so rows stay
+   comparable across the two release-note eras:
+   - prs / contributors / firstTimers: use the figure the body states outright
+     ("merged 930 PRs from 125 contributors", "welcome 14 new contributors").
+     Where the body only lists first-timers without a total, count the list.
+     Omit rather than derive: v1.0.0 states commits, not PRs, so prs is absent,
+     and v1.2.0 names no first-timers at all.
+   - breaking: top-level entries under Breaking Changes, including its
+     Deprecated/Removed subsections, but excluding subsections that only
+     restate a prior release's announced deprecations ("vX.Y.Z
+     Future-Deprecation Reminders"). Pre-v1.0.0 bodies have no Breaking Changes
+     section; v0.9.0's lone Deprecation Notices entry is the same entry class
+     and counts, and a release with no such section at all is a true 0.
+   - knownIssues: one per named issue — the per-issue heading where the body
+     gives each issue its own, otherwise the top-level bullets.
+   Known exception: v1.0.0 breaking is published as 41, but its body holds 40
+   top-level entries and no rule reproduces 41. Left as published.
+
+   The absent prs and contributors cells are absent for cause, not for want of
+   looking. Neither the release bodies, the TPM release archive, nor the git
+   history yields a figure comparable to the stated ones: the archive's own
+   numbers disagree with each other (v0.9.0 is written up as both 217 and 935
+   PRs for the identical window, and v1.0.0's 708 is quoted as commits in one
+   place and as merged PRs in another), and no tag-to-tag count reproduces the
+   three published anchors — the closest method returns 910/572/899 against a
+   published 930/603/896, missing in both directions, so it cannot be trusted
+   to fill the rest. Leave them absent unless a method reproduces all three. */
 export const RELEASE_STATS: Record<string, ReleaseStats> = {
   "v1.3.0": { prs: 930, contributors: 125, firstTimers: 23, breaking: 24, knownIssues: 10 },
   "v1.2.0": { prs: 603, contributors: 82, breaking: 5, knownIssues: 11 },
   "v1.1.0": { prs: 896, contributors: 113, firstTimers: 12, breaking: 8, knownIssues: 20 },
   "v1.0.0": { contributors: 90, firstTimers: 34, breaking: 41, knownIssues: 14 },
+  "v0.9.0": { firstTimers: 14, breaking: 1, knownIssues: 13 },
+  "v0.8.0": { firstTimers: 20, breaking: 0, knownIssues: 14 },
+  "v0.7.0": { firstTimers: 2, breaking: 0, knownIssues: 7 },
+  "v0.6.0": { firstTimers: 4, breaking: 0, knownIssues: 3 },
 };
 
 export const NIGHTLIES_NOTE =

@@ -8,7 +8,6 @@ subtitle: Hardware, platform, and feature support for Dynamo backends
 import { ReferenceStyles } from "@/components/ReferenceStyles";
 import { CompatibilityHero } from "@/components/CompatibilityHero";
 import { FeatureHeatmap } from "@/components/FeatureHeatmap";
-import { RunsWhereWizard } from "@/components/RunsWhereWizard";
 
 <ReferenceStyles />
 
@@ -20,11 +19,118 @@ For extended driver compatibility beyond the listed minimums, including forward
 See [Release Artifacts](release-artifacts.mdx) for the full artifact inventory — container images, wheels, Helm charts, and crates — and [Model Early Access Builds](model-early-access-builds.mdx) for per-model early access container builds.
 </Note>
 
-## Find a Compatible Release
+## Release Support Matrix
 
-Pick your backend and the CUDA generation your host driver supports to see which Dynamo releases you can run — and what to pull for the current one.
+The card above covers one release at a time. Expand the matrix below to compare CUDA toolkit and minimum driver requirements across releases, per backend.
 
-<RunsWhereWizard />
+{/* support-matrix:begin — generated by scripts/gen_llms_tables.py, do not edit */}
+
+<Accordion title="CUDA toolkit and minimum driver by release">
+
+Every released line — stable releases and their patches, grouped by minor line, newest first. Platform previews and model-specific builds are not listed individually; those with a documented toolkit requirement appear in the notes below, and [Releases (machine-readable)](releases-machine-readable.mdx) has the full release inventory.
+
+**1.3.x**
+
+| Dynamo | Backend | CUDA Toolkit | Min Driver | Note |
+| --- | --- | --- | --- | --- |
+| 1.3.0 | SGLang | 13.0 | 580.xx+ | - |
+| 1.3.0 | TensorRT-LLM | 13.1 | 580.xx+ | - |
+| 1.3.0 | vLLM | 13.0 | 580.xx+ | - |
+
+**1.2.x**
+
+| Dynamo | Backend | CUDA Toolkit | Min Driver | Note |
+| --- | --- | --- | --- | --- |
+| 1.2.1 | SGLang | 12.9 | 575.xx+ | - |
+| 1.2.1 | SGLang | 13.0 | 580.xx+ | - |
+| 1.2.1 | TensorRT-LLM | 13.1 | 580.xx+ | - |
+| 1.2.1 | vLLM | 12.9 | 575.xx+ | - |
+| 1.2.1 | vLLM | 13.0 | 580.xx+ | - |
+| 1.2.0 | SGLang | 12.9 | 575.xx+ | - |
+| 1.2.0 | SGLang | 13.0 | 580.xx+ | - |
+| 1.2.0 | TensorRT-LLM | 13.1 | 580.xx+ | - |
+| 1.2.0 | vLLM | 12.9 | 575.xx+ | - |
+| 1.2.0 | vLLM | 13.0 | 580.xx+ | - |
+
+**1.1.x**
+
+| Dynamo | Backend | CUDA Toolkit | Min Driver | Note |
+| --- | --- | --- | --- | --- |
+| 1.1.1 | SGLang | 12.9 | 575.xx+ | - |
+| 1.1.1 | SGLang | 13.0 | 580.xx+ | - |
+| 1.1.1 | TensorRT-LLM | 13.1 | 580.xx+ | - |
+| 1.1.1 | vLLM | 12.9 | 575.xx+ | - |
+| 1.1.1 | vLLM | 13.0 | 580.xx+ | - |
+| 1.1.0 | SGLang | 12.9 | 575.xx+ | - |
+| 1.1.0 | SGLang | 13.0 | 580.xx+ | - |
+| 1.1.0 | TensorRT-LLM | 13.1 | 580.xx+ | - |
+| 1.1.0 | vLLM | 12.9 | 575.xx+ | - |
+| 1.1.0 | vLLM | 13.0 | 580.xx+ | - |
+
+**1.0.x**
+
+| Dynamo | Backend | CUDA Toolkit | Min Driver | Note |
+| --- | --- | --- | --- | --- |
+| 1.0.2 | SGLang | 12.9 | 575.xx+ | - |
+| 1.0.2 | SGLang | 13.0 | 580.xx+ | - |
+| 1.0.2 | TensorRT-LLM | 13.1 | 580.xx+ | - |
+| 1.0.2 | vLLM | 12.9 | 575.xx+ | - |
+| 1.0.2 | vLLM | 13.0 | 580.xx+ | - |
+| 1.0.1 | SGLang | 12.9 | 575.xx+ | - |
+| 1.0.1 | SGLang | 13.0 | 580.xx+ | - |
+| 1.0.1 | TensorRT-LLM | 13.1 | 580.xx+ | - |
+| 1.0.1 | vLLM | 12.9 | 575.xx+ | - |
+| 1.0.1 | vLLM | 13.0 | 580.xx+ | - |
+| 1.0.0 | SGLang | 12.9 | 575.xx+ | - |
+| 1.0.0 | SGLang | 13.0 | 580.xx+ | - |
+| 1.0.0 | TensorRT-LLM | 13.1 | 580.xx+ | - |
+| 1.0.0 | vLLM | 12.9 | 575.xx+ | - |
+| 1.0.0 | vLLM | 13.0 | 580.xx+ | - |
+
+**0.9.x**
+
+| Dynamo | Backend | CUDA Toolkit | Min Driver | Note |
+| --- | --- | --- | --- | --- |
+| 0.9.1 | SGLang | 12.9 | 575.xx+ | - |
+| 0.9.1 | TensorRT-LLM | 13.0 | 580.xx+ | - |
+| 0.9.1 | vLLM | 12.9 | 575.xx+ | - |
+| 0.9.0 | SGLang | 12.9 | 575.xx+ | - |
+| 0.9.0 | TensorRT-LLM | 13.0 | 580.xx+ | - |
+| 0.9.0 | vLLM | 12.9 | 575.xx+ | - |
+
+**0.8.x**
+
+| Dynamo | Backend | CUDA Toolkit | Min Driver | Note |
+| --- | --- | --- | --- | --- |
+| 0.8.1 | SGLang | 12.9 | 575.xx+ | - |
+| 0.8.1 | SGLang | 13.0 | 580.xx+ | Experimental |
+| 0.8.1 | TensorRT-LLM | 13.0 | 580.xx+ | - |
+| 0.8.1 | vLLM | 12.9 | 575.xx+ | - |
+| 0.8.1 | vLLM | 13.0 | 580.xx+ | Experimental |
+| 0.8.0 | SGLang | 12.9 | 575.xx+ | - |
+| 0.8.0 | SGLang | 13.0 | 580.xx+ | Experimental |
+| 0.8.0 | TensorRT-LLM | 13.0 | 580.xx+ | - |
+| 0.8.0 | vLLM | 12.9 | 575.xx+ | - |
+| 0.8.0 | vLLM | 13.0 | 580.xx+ | Experimental |
+
+**0.7.x**
+
+| Dynamo | Backend | CUDA Toolkit | Min Driver | Note |
+| --- | --- | --- | --- | --- |
+| 0.7.1 | SGLang | 12.8 | 570.xx+ | - |
+| 0.7.1 | TensorRT-LLM | 13.0 | 580.xx+ | - |
+| 0.7.1 | vLLM | 12.9 | 575.xx+ | - |
+| 0.7.0 | SGLang | 12.9 | 575.xx+ | - |
+| 0.7.0 | TensorRT-LLM | 13.0 | 580.xx+ | - |
+| 0.7.0 | vLLM | 12.8 | 570.xx+ | - |
+
+- Patch versions (e.g. v0.8.1.post1, v0.7.0.post1) have the same CUDA support as their base version.
+- Early access v1.1.0-dev.* images follow the same CUDA matrix as v1.0.2. The v1.2.0-deepseek-v4-dev.3 vLLM container is CUDA 13.0 multi-arch; the SGLang containers split by arch (CUDA 12.9 on amd64, CUDA 13.0 on arm64).
+- Experimental CUDA 13 images are not published for all versions.
+
+</Accordion>
+
+{/* support-matrix:end */}
 
 ## Platform Notes
 

@@ -237,6 +237,10 @@ Release highlights (stable releases):
 | v1.2.0 | 603 | 82 | - | 5 | 11 |
 | v1.1.0 | 896 | 113 | 12 | 8 | 20 |
 | v1.0.0 | - | 90 | 34 | 41 | 14 |
+| v0.9.0 | - | - | 14 | 1 | 13 |
+| v0.8.0 | - | - | 20 | 0 | 14 |
+| v0.7.0 | - | - | 2 | 0 | 7 |
+| v0.6.0 | - | - | 4 | 0 | 3 |
 
 ## Nightlies
 

@@ -21,3 +21,22 @@ Agents and automation: [Releases (machine-readable)](../releases-machine-readabl
 ## Releases
 
 <ReleaseTimeline />
+
+{/* release-stats:begin — generated by scripts/gen_llms_tables.py, do not edit */}
+
+## Release statistics
+
+Counts taken from each release's GitHub body. A dash means the count was not recorded for that release, not that it was zero.
+
+| Release | PRs | Contributors | First-time contributors | Breaking changes | Known issues |
+| --- | --- | --- | --- | --- | --- |
+| v1.3.0 | 930 | 125 | 23 | 24 | 10 |
+| v1.2.0 | 603 | 82 | - | 5 | 11 |
+| v1.1.0 | 896 | 113 | 12 | 8 | 20 |
+| v1.0.0 | - | 90 | 34 | 41 | 14 |
+| v0.9.0 | - | - | 14 | 1 | 13 |
+| v0.8.0 | - | - | 20 | 0 | 14 |
+| v0.7.0 | - | - | 2 | 0 | 7 |
+| v0.6.0 | - | - | 4 | 0 | 3 |
+
+{/* release-stats:end */}