[ko3n1g]

Summary

• Bumps NVIDIA-NeMo/FW-CI-templates reference in build-docs.yml from v0.57.0 to v0.80.2
• v0.80.2 includes retry with exponential backoff for Sphinx linkcheck to handle transient failures

Test plan

• Verify the build-docs workflow triggers and passes after this bump

Summary by CodeRabbit

• Chores
  • Updated documentation build workflow infrastructure to latest version.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the build-docs job's reusable workflow reference in GitHub Actions from version 0.57.0 to 0.80.2, maintaining all existing job conditionals and dependencies.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration .github/workflows/build-docs.yml	Bumped reusable workflow version from v0.57.0 to v0.80.2 for the upstream _build_docs.yml workflow reference.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: bumping FW-CI-templates to v0.80.2 in the build-docs workflow configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Test Results For Major Changes	✅ Passed	This PR contains only minor changes—a single version pin update in CI/CD workflow configuration that does not affect codebase functionality, numerics, convergence, or performance.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ko3n1g/chore/bump-fw-ci-templates-v0.80.2

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/build-docs.yml:
- Line 35: Update the workflow action reference on the uses line in
build-docs.yml: replace the non-existent tag "v0.80.2" in the string
"NVIDIA-NeMo/FW-CI-templates/.github/workflows/_build_docs.yml@v0.80.2" with a
valid existing tag such as "v0.80.1" (or another confirmed upstream tag) so the
workflow uses an available release.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6233f9da-a370-40af-8cf7-15968fd36dd3

📥 Commits

Reviewing files that changed from the base of the PR and between ba68841 and 03996f4.

📒 Files selected for processing (1)

• .github/workflows/build-docs.yml

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "1) Verify tag exists:"
git ls-remote --tags https://github.com/NVIDIA-NeMo/FW-CI-templates.git refs/tags/v0.80.2

echo
echo "2) Inspect _build_docs.yml at v0.80.2 for linkcheck retry/backoff related config:"
gh api repos/NVIDIA-NeMo/FW-CI-templates/contents/.github/workflows/_build_docs.yml?ref=v0.80.2 \
  | jq -r '.content' | base64 -d \
  | rg -n -C2 'linkcheck|retry|backoff'

Repository: NVIDIA-NeMo/Megatron-Bridge

Length of output: 223

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Attempt to verify tag exists using git ls-remote with simpler output
echo "Checking if v0.80.2 tag exists in FW-CI-templates repository:"
git ls-remote --tags https://github.com/NVIDIA-NeMo/FW-CI-templates.git | grep -E 'v0\.80\.2' || echo "Tag v0.80.2 not found"

echo ""
echo "Listing recent tags to see available versions:"
git ls-remote --tags https://github.com/NVIDIA-NeMo/FW-CI-templates.git | tail -20

Repository: NVIDIA-NeMo/Megatron-Bridge

Length of output: 1378

---

🌐 Web query:

NVIDIA-NeMo FW-CI-templates v0.80.2 release tag build docs workflow

💡 Result:

The NVIDIA-NeMo/FW-CI-templates repository provides centralized GitHub Actions CI/CD workflow templates for NeMo Framework (NeMo-FW) libraries. No specific v0.80.2 release tag, build docs, or workflow details were found in searches across GitHub releases, PRs, tags, or official NVIDIA docs as of 2026-03-20. The repo is active with recent activity (e.g., 2026-03-14), used in NeMo PRs for builds (e.g., PR #11077 switches to FW templates), releases (PR #11180 adds release workflow), and dependency bumps (PR #13482). Check the repo directly: https://github.com/NVIDIA-NeMo/FW-CI-templates/releases and https://github.com/NVIDIA-NeMo/FW-CI-templates/tree/main/.github/workflows for latest templates. No dedicated build documentation identified; workflows are standard GitHub Actions YAML files triggered by labels like "Run CICD".

Citations:

• 1: https://github.com/NVIDIA/NeMo-FW-CI-templates/releases
• 2: https://github.com/NVIDIA-NeMo/FW-CI-templates
• 3: ci: Switch to FW templates for build Speech#11077
• 4: https://github.com/NVIDIA-NeMo/FW-CI-templates/actions
• 5: ci: Add release workflow Speech#11180

---

Tag v0.80.2 does not exist—update to an existing version before merge.

The referenced upstream template version v0.80.2 does not exist in the NVIDIA-NeMo/FW-CI-templates repository. Available versions are v0.80.1, v0.80.0, and earlier. This will cause the workflow to fail at runtime. Update line 35 to use v0.80.1 or confirm the correct version number with the upstream repository.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/build-docs.yml at line 35, Update the workflow action
reference on the uses line in build-docs.yml: replace the non-existent tag
"v0.80.2" in the string
"NVIDIA-NeMo/FW-CI-templates/.github/workflows/_build_docs.yml@v0.80.2" with a
valid existing tag such as "v0.80.1" (or another confirmed upstream tag) so the
workflow uses an available release.