Skip to content

docs: rebrand main docs to 26.08 for RC GitHub Pages QA - #2430

Merged
kheiss-uwzoo merged 18 commits into
NVIDIA:mainfrom
kheiss-uwzoo:docs/26.08-gh-pages-version-cutover
Aug 11, 2026
Merged

docs: rebrand main docs to 26.08 for RC GitHub Pages QA#2430
kheiss-uwzoo merged 18 commits into
NVIDIA:mainfrom
kheiss-uwzoo:docs/26.08-gh-pages-version-cutover

Conversation

@kheiss-uwzoo

@kheiss-uwzoo kheiss-uwzoo commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

Summary

Rebrand reader-facing version strings on main from 26.05 to 26.08 / 26.8.0 so GitHub Pages matches what QA reviews during 26.08 RC readiness.

  • Release notes heading + short RC/Pages vs docs.nvidia.com callout
  • Install RC example (26.08-RC1)
  • Helm README / OpenShift image tag examples and minimal-install anchors (…-2608)
  • Cross-doc links to the recommended minimal install section

Out of scope

  • Litmus README first-run / LanceDB callout (was folded in briefly; removed — use a separate PR if needed)
  • Full 26.08 release-notes body rewrite (docs(extraction): add 26.08 release notes for post-26.05 changes #2434)
  • docs/publish/versions.json and docs.nvidia.com publish workflow (still frozen on 26.05)
  • Helm Chart.yaml / values.yaml runtime defaults (eng when RC artifacts exist)

Merge timing

Hold as draft until Jeremy cuts the 26.08 RC; then undraft and merge so Pages shows 26.08 for QA. Safe to merge after the cut even if not in the same minute as the tag.

Test plan

  • After merge, GitHub Pages shows 26.08 in release notes heading and Helm README examples
  • docs.nvidia.com version picker still lists 26.5.0 until a separate publish
  • Spot-check anchors to #recommended-minimal-install-2608
  • Confirm nemo_retriever/README.md only changes the 26.08-RC1 install example (no Litmus first-run edits)

Align reader-facing version strings on main with the 26.08 release candidate so GitHub Pages matches what QA uses for readiness analysis, while leaving docs.nvidia.com publish metadata on the frozen 26.05 snapshot.
@kheiss-uwzoo kheiss-uwzoo self-assigned this Aug 4, 2026
@kheiss-uwzoo kheiss-uwzoo added doc Improvements or additions to documentation 26.08 labels Aug 4, 2026
Address Litmus Docs Readiness P1/P2 findings without changing CLI or library behavior: promote the corpus-size warning, point first ingest at data/, and correct libeoffice.
Replace absolute single-PDF failure wording with skip/clamp guidance so the Litmus first-run README matches current LanceDB indexing on main.
@kheiss-uwzoo kheiss-uwzoo changed the title docs: rebrand main for 26.08 RC GitHub Pages QA review docs: 26.08 RC readiness (rebrand + Litmus README first-run) Aug 11, 2026
Correct a bad rebrand edit that downgraded llama-nemotron-embed-vl-1b-v2 from 2.3.0 to 2.0.0, and prefer refer-to wording in the first-run LanceDB callouts.
Keep NVIDIA#2430 focused on 26.08 nomenclature for GitHub Pages QA. Litmus first-run guidance can return in a separate PR.
@kheiss-uwzoo kheiss-uwzoo changed the title docs: 26.08 RC readiness (rebrand + Litmus README first-run) docs: rebrand main docs to 26.08 for RC GitHub Pages QA Aug 11, 2026
Release notes link to this release's Helm README and graph README. main drifts past 26.08, so anchor these to the 26.08 release branch like 26.05 docs used blob/26.05.
Drop the Pages-vs-docs.nvidia.com RC callout from release notes, and replace GA product-status wording with supported/published language in the root README, release notes, and Helm README.
…elease

26.08 is not stable yet, so the README should not advertise it as the latest supported line.
@kheiss-uwzoo
kheiss-uwzoo marked this pull request as ready for review August 11, 2026 20:22
@kheiss-uwzoo
kheiss-uwzoo requested review from a team as code owners August 11, 2026 20:22
@kheiss-uwzoo
kheiss-uwzoo requested a review from jioffe502 August 11, 2026 20:22
@greptile-apps

greptile-apps Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR updates reader-facing documentation for the 26.08 RC while retaining the chart’s checked-in 26.5.0 default.

  • Updates release headings, release links, installation examples, and minimal-install anchors to 26.08.
  • Explicitly overrides the service image to 26.8.0 in 26.08 Helm and OpenShift installation examples.
  • Keeps the Helm default and values reference aligned with the current 26.5.0 chart configuration.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename Overview
docs/docs/extraction/releasenotes.md Rebrands the current release heading and repository links from 26.05 to 26.08.
nemo_retriever/README.md Updates the prerelease installation example to 26.08-RC1.
nemo_retriever/helm/README.md Updates 26.08 anchors and adds an explicit 26.8.0 image override while accurately retaining the chart’s 26.5.0 default.
nemo_retriever/helm/openshift.md Updates both OpenShift installation examples to deploy the 26.8.0 service image.

Reviews (4): Last reviewed commit: "docs(26.08): pin service image in minima..." | Re-trigger Greptile

Comment thread nemo_retriever/helm/README.md
Chart defaults are still 26.5.0; documenting 26.8.0 as the default was incorrect until the RC eng cut bumps Chart.yaml and values.yaml.
@kheiss-uwzoo

Copy link
Copy Markdown
Collaborator Author

@greptile review

Ensure the 26.08-labeled command deploys the intended service image while the chart default remains 26.5.0 until the engineering release cut.
@kheiss-uwzoo

Copy link
Copy Markdown
Collaborator Author

@greptile review

@kheiss-uwzoo
kheiss-uwzoo merged commit d0851ee into NVIDIA:main Aug 11, 2026
5 of 7 checks passed
kheiss-uwzoo added a commit to kheiss-uwzoo/nv-ingest that referenced this pull request Aug 11, 2026
Follow-up after NVIDIA#2430: the Helm README section was rebranded to 26.08, but the unit test marker still expected 26.05.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

26.08 doc Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants