ci(docs): publish 26.8.1 docs.nvidia.com from main - #2583
Merged
kheiss-uwzoo merged 4 commits intoAug 25, 2026
Conversation
The version folder is already 26.8.1, but the build still checked out tag 26.08. Point content at freeze branch 26.08.1.
kheiss-uwzoo
requested review from
drobison00 and
jperez999
and removed request for
drobison00
August 25, 2026 16:37
Contributor
Greptile SummaryThe PR updates the manual docs.nvidia.com publishing workflow to build from the triggering commit, publish the 26.8.1 release metadata, and fail closed for any future non-manual event.
|
| Filename | Overview |
|---|---|
| .github/workflows/nrl-docs-nvidia-publish.yml | Updates source-revision handling and adds a fail-closed non-dispatch guard while retaining explicit manual publication controls. |
| docs/publish/versions.json | Adds the existing 26.5.0 documentation release to the picker while retaining 26.8.1 as latest. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
Dispatch[Manual workflow dispatch] --> Resolve[Resolve version and publish inputs]
Other[Future non-dispatch event] --> Closed[Force dry-run and disable latest update]
Resolve --> Checkout[Checkout triggering commit]
Closed --> Checkout
Checkout --> Build[Build MkDocs site]
Build --> Metadata[Copy versions.json into artifact]
Metadata --> Publish[Invoke docs publishing action]
Publish --> Version[Publish versioned documentation]
Publish --> Latest{Publish as latest?}
Latest -->|Explicit manual selection| Alias[Update latest alias]
Latest -->|No or dry-run| Preserve[Preserve current latest alias]
Reviews (5): Last reviewed commit: "ci(docs): pin publish checkout to the tr..." | Re-trigger Greptile
26.08 docs are built from main, not a freeze branch. Checkout main and copy versions.json from that tree; keep the publish folder as 26.8.1.
Force dry-run unless the run is workflow_dispatch, so a re-added push trigger cannot overwrite latest/. Restore 26.5.0 in versions.json so the 26.08.1 cutover does not hide the prior GA train.
Use github.sha so the 26.8.1 cutover can dispatch this branch (picker + fail-closed workflow) without waiting on code-owner merge, and so a delayed run cannot publish a newer tip.
jperez999
approved these changes
Aug 25, 2026
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
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.
Summary
mainand publish as26.8.1/latest.workflow_dispatchevents cannot write S3 or movelatest/(the Aug 19 leak).26.5.0and26.3.0in the version picker.Test plan
mainstill checks out tag26.08)workflow_dispatchwith version26.8.1andpublish-as-latest: true