Repository navigation
docs: publish 1.0.3 with legacy Self-Managed 0.6.2 notes - #2256
Conversation
Run a live Fern link check after publication, weekly, or on demand. Retain the source-page report and reject incomplete scans while reporting blocked destinations separately. Relates to #2214 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
Correct the Dynamo 1.4.1 guide URL and pin the KAI template download to its verified source. Render the OTLP endpoint example as code and document authentication limitations in Fern reports. Relates to #2254 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
Replace the scheduled published-site scan with changed-file HTTP checks inside the existing required docs job, including merge-queue runs. Keep Fern internal and Development checks and retain the link report on failure. Add checksum-pinned Lychee 0.24.2 for Markdown and MDX parsing and HTTP validation. Its MIT license is allowed; add CI attribution and regenerate NOTICE. Relates to #2254 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
Run the required docs validation workflow when a documentation PR targets another docs branch, so phased review has the same link checks before retargeting main. Relates to #2254 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 10 remain after this review. 📝 WalkthroughWalkthroughThe changes add a 0.6.1-to-0.6.2 upgrade guide and revise the 1.0.1 upgrade guide to start from 0.6.2. They also update changelogs, navigation, edition settings, and manual preview configuration. ChangesSelf-Managed upgrade and documentation release
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Other Merge Risk: ⚪ Minimal · up to The 1.0.3 edition points to the current release snapshot, including the corrected upgrade title and navigation. No release-blocking documentation mismatch is established; proceed with normal integration checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
🌿 Preview your docs: https://nvidia-preview-docs-2195-release-1-0-3.docs.buildwithfern.com/nvcf Here are the markdown pages you've updated: |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Use the parent commit when a push event has an all-zero previous ref and ensure explicitly selected tracked Markdown is not skipped by ignore files. Cover the initial-push fallback in the fixture tests. Relates to #2254 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
721ac63 to
2a2d641
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
Relates to #2254 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
Add a concise native changelog entry and the focused patch upgrade guide. Update the existing onward migration URL to require the patch, retain pod-create waits, and document the recorded availability limits. Prepare the 1.0.3 docs-only release note without changing the selected stack combination. Relates to #2191 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
Keep existing deep links to the starting-state checks valid after documenting the intermediate 0.6.2 patch. Relates to #2191 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
Pin the tested immutable release commit before changing the default selector. Advance Development to 1.0.4 and allow canonical hosted previews to verify the remote release refs before publication. Relates to #2214 Signed-off-by: Stephanie Baum <sbaum@nvidia.com>
2a2d641 to
dea7619
Compare
|
This PR is included in version 1.29.3. The release is available on GitHub release. |
|
This PR is included in version 1.69.1. The release is available on GitHub release. |
|
This PR is included in version 1.25.1. The release is available on GitHub release. |
|
This PR is included in version 1.14.2. The release is available on GitHub release. |
|
This PR is included in version 1.10.1. The release is available on GitHub release. |
|
This PR is included in version 0.5.1. The release is available on GitHub release. |
|
This PR is included in version 0.9.1. The release is available on GitHub release. |
TL;DR
Publish docs-only release 1.0.3 with the legacy Self-Managed 0.6.2 release notes, its focused patch upgrade procedure, and the link repairs from #2253. The default stack combination remains Self-Managed 1.0.1, Compute Plane 1.0.0, and Observability 1.0.0.
Additional Details
docs/releases/1.0.3at4890d84c89d0cfb0bc313a54afc3ecee02a098f9as the default. Its source is the reviewed content commitc8467efa641a60d29dd2a25acf043b827310d7d5. Advance Development to 1.0.4. The existing 1.0.1 and 1.0.2 branch heads remain unchanged.preview=canonicalto the manual Fern preview workflow so operators can validate the exact published configuration and remote refs before a cutover.For the Reviewer
#2253 is merged, and this PR targets main. The corrected 1.0.3 release branch already exists and is pinned above. Its effective rules again prohibit updates, deletion, and force pushes with no bypass actors; the user-approved unpublished correction was applied with an exact lease and protection was immediately restored and verified. Merging this PR has no branch-creation dependency.
The guide title, sidebar label, and release-note index now say 0.6.2 to 1.0.1. The existing URL and anchor remain valid. The corrected release preview passed rendered heading, sidebar, link, and anchor checks.
Start with the short 0.6.2 changelog entry, then the new patch procedure, then the existing onward guide's diff. Earlier 0.6.0-to-0.6.1 corrections from #2195 remain tracked by #2191; they are not silently copied into historical snapshots in this port.
For QA
Passed locally: canonical docs/release checks, Development layout validation, external links in the changed Markdown, Markdown lint, 43 parsed Bash snippets, and failure fixtures for pod deletion, creation wait, readiness, and OpenBao status. Verified that existing onward-guide pod-create/wait snippets remain intact.
The fresh stable 0.6.2-to-1.0.1 k3d rehearsal completed on 2026-10-04 as a user-approved limited function/deployment diagnostic. It reached Self-Managed 1.0.1 and Compute Plane 1.0.0 with NVCA/operator 3.10.0. Both full target control-plane and compute installs passed their repeat syncs.
This is not a clean pass of the unmodified guide. Local QA required same-version upstream helper images (#2197), an explicit receipt version because the published 1.0.1 bundle contains VERSION=1.0.0 (#2258), and an explicit local profile after released CLI 1.16.2 hit the disabled-LLM PKI export bug described in #1550. The packaged VERSION file and released CLI were not edited. The active-instance API timestamps changed despite preserved underlying records (#2199). Cassandra/OpenBao backups were exported and checked; restore and durable queued-message retention were not exercised. Physical GPUs, ingress/TLS, optional add-ons, separate observability, and shared storage were outside this ARM64 single-host k3d test. Full qualification requires a new source run after resolving the blockers.
The earlier rehearsal's results remain accurately described in the guide; this new diagnostic's details are recorded here without modifying the frozen release content. Anonymous NGC resource access returned 403, so the instructions require obtaining and verifying the exact bundle through the operator's artifact distribution channel without claiming guest availability.
Hosted validation:
Edition tooling tests passed. The prepared stack manifest, including source commits and inventory URLs, matches 1.0.2 exactly. On final head
5b28f0a7e364699a2d2b3d147edee4f437bb7ca3, all triggered CI checks and CodeRabbit pass. There are no unresolved review threads or merge conflicts; GitHub still requires review approval. The corrected release branch is already present and protected. No production publication or PR merge was triggered by this preparation.Dependencies
No additional dependency changes beyond #2253. No runtime artifact changes or additional license/NOTICE impact.
Issues
Relates to #2191
Relates to #2214
Relates to #2254
Related PRs: #2195 (source content), #2190 (stack patch), #2253 (link checks and repairs).
Checklist
Summary by CodeRabbit