Prerequisites

• I searched existing issues and found no duplicates
• I can reproduce this issue consistently
• This is not a security vulnerability

Bug Description

When the publish workflow triggers on the latest release tag (e.g. v0.13.0), it registers a separate version entry in docs.yml even though the "Latest · v0.13.0" stamp already covers it. This creates a duplicate in the version dropdown.

Additionally, if versions are registered out of order (e.g. backporting a patch release), the dropdown order is insertion-based rather than semver-sorted.

Impact

Medium (workaround exists)

Component

Docs / examples

Regression?

No, this is a new use case

Steps to Reproduce

1. Push a release tag that matches the current latest GitHub release
2. Workflow registers a version entry AND stamps Latest — duplicate in dropdown
3. Register an older backport release — appears at wrong position in dropdown

Expected Behavior

• Latest release tag should skip version registration (Latest stamp covers it)
• Version entries should be sorted by semver descending

Actual Behavior

• Duplicate entry for latest release
• Insertion order preserved instead of semver sort

Already fixed in NVIDIA/NVSentinel#1315 and NVIDIA/topograph#338.