ci: Update release-docs workflow to use FW-CI-templates v0.72.0

[chtruong814]

What does this PR do ?

ci: Update release-docs workflow to use FW-CI-templates v0.72.0

The latest tag in some repos was whatever was published from main branch. However, we will now designate "latest" as the latest stable version. A follow-up change will include publshing docs as part of the release repo workflow. And we will also begin to publish "nightly" docs from the main branch.

Issues

List issues that this PR closes (syntax):

Usage

• You can potentially add a usage example below

# Add a code snippet demonstrating how to use this

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you run the unit tests and functional tests locally? Visit our Testing Guide for how to run tests
• Did you add or update any necessary documentation? Visit our Document Development Guide for how to write, build and test the docs.

Additional Information

• ...

Summary by CodeRabbit

• Chores
  • Added new workflow input to control whether releases are published as the latest version (enabled by default)
  • Updated CI/CD infrastructure dependencies

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the release-docs workflow by introducing a new optional workflow input publish-as-latest (defaulting to true), bumping the FW-CI-templates reference from v0.71.0 to v0.72.0, and dynamically parameterizing the overwrite-latest-on-tag setting based on the new input.

Changes

Cohort / File(s)	Summary
Release Docs Workflow Configuration .github/workflows/release-docs.yml	Added new workflow input publish-as-latest (boolean, default true); upgraded FW-CI-templates reference to v0.72.0; changed overwrite-latest-on-tag from static false to dynamic input-driven value.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• ci: Fix docs publishing #1898: Modifies the same release-docs workflow file with similar pattern changes (adding inputs and updating FW-CI-templates reference).
• ci: Add docs publishing job for 0.5.0 #1896: Updates the same workflow file and related publishing logic including overwrite-latest-on-tag behavior.
• ci: Add docs publishing job for 0.4.0 #1897: Introduces the initial release-docs workflow that this PR builds upon and refines.

Suggested labels

CI, CI:docs

Suggested reviewers

• ko3n1g
• terrykong

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 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 primary change—updating the release-docs workflow to use FW-CI-templates v0.72.0, which is the main change evident in the raw summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main
Test Results For Major Changes	✅ Passed	PR contains only minor CI/CD workflow configuration changes to documentation publishing, not affecting runtime behavior, 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
• Post copyable unit tests in a comment
• Commit unit tests in branch chtruong/update-release-docs-latest

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/release-docs.yml (1)

52-57: ⚠️ Potential issue | 🟡 Minor

Stale inline comment — no longer reflects the new behavior.

These comments still describe the old behavior where running on main publishes to the "latest" directory. With overwrite-latest-on-tag now driven by the publish-as-latest input, "latest" is controlled explicitly and is no longer tied to being on main. Please update or remove the comment to avoid confusion.

✏️ Suggested comment update

       - uses: ./FW-CI-templates/.github/actions/publish-docs
-        # This workflow runs either on main, or on a version tag. Any other git ref will lead
-        # to an error.
-        # If its on main, it will publish to "latest" directory in Akamai.
-        # If its on a versioned tag, it will extract the version number from the tag (strip `v` prefix)
-        # and publish to the versioned directory in Akamai.
+        # This workflow runs either on main or on a version tag. Any other git ref will lead
+        # to an error.
+        # On a versioned tag, it extracts the version number (strips `v` prefix) and publishes
+        # to the versioned directory in Akamai. If publish-as-latest is true, it also overwrites
+        # the "latest" directory.