ci: Update release-docs workflow to use FW-CI-templates v0.72.0#726
Open
chtruong814 wants to merge 1 commit intomainfrom
Open
ci: Update release-docs workflow to use FW-CI-templates v0.72.0#726chtruong814 wants to merge 1 commit intomainfrom
chtruong814 wants to merge 1 commit intomainfrom
Conversation
Signed-off-by: Charlie Truong <chtruong@nvidia.com>
ko3n1g
approved these changes
Feb 16, 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
2 participants
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.
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.
Will need to sync with Evaluator team on what their plans are for their docs especially given the automated releases.