Add short cu12/cu13 Docker tag aliases and update docs

[ramakrishnap-nv]

Publishes short cu<major> Docker image tags (latest-cu12, latest-cu13, <version>-cu12/cu13) as aliases of the existing fully-qualified -cuda<minor>-py<py> tags, matching the pip/conda wheel suffix convention. The fully-qualified tags are unchanged — this is purely additive on the publish side.

Docs (README, install-selector, NIM operator examples, gRPC examples) and the regression config now lead with the short tags.

Note: short aliases only exist for builds after this change lands (26.6.0+). Skill docs/evals are tracked in #1369.

🤖 Generated with Claude Code

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6c6c76d5-f4f2-4d9c-9258-286bb8a77df9

📥 Commits

Reviewing files that changed from the base of the PR and between b9e4eb6 and 9356e1e.

📒 Files selected for processing (2)

• ci/docker/create_multiarch_manifest.sh
• docs/cuopt/source/cuopt-server/nim-operator/guide/deploy.sh

🚧 Files skipped from review as they are similar to previous changes (2)

• docs/cuopt/source/cuopt-server/nim-operator/guide/deploy.sh
• ci/docker/create_multiarch_manifest.sh

---

📝 Walkthrough

Walkthrough

This PR standardizes cuOpt Docker image tagging from verbose CUDA/Python-specific formats to simplified tags based on CUDA major version (cu12, cu13). The manifest generation script creates the new tags, documentation explains the scheme, interactive tooling generates commands using the new tags, and deployment examples demonstrate their usage.

Changes

Docker image tagging scheme migration from CUDA/Python-suffixed to simplified tags

Layer / File(s)	Summary
Multi-architecture manifest generation for simplified tags ci/docker/create_multiarch_manifest.sh	Docker manifest script derives CUDA_MAJOR from CUDA_SHORT and generates additional multi-architecture manifest tags ending with -cu${CUDA_MAJOR} for both Docker Hub and NVCR staging, alongside existing per-architecture cuda${CUDA_SHORT}-py${PYTHON_SHORT} image references. SPDX copyright header updated to 2025-2026.
Documentation of new tagging scheme README.md, docs/cuopt/source/cuopt-grpc/advanced.rst, docs/cuopt/source/cuopt-server/nim-operator/configuration.rst	README documents the new latest-cu12/latest-cu13 and <version>-cu12/<version>-cu13 tagging scheme with nightly variants. gRPC and NIM operator configuration documentation updated with example tags using the new format.
Install selector command generation updates docs/cuopt/source/_static/install-selector.js	Install selector JavaScript updates container command templates to generate docker pull and docker run commands with new stable tags (latest-cu12/latest-cu13) and nightly tags for both library and server interfaces. Default tag fallback updated to latest-cu12.
Deployment configurations and examples docs/cuopt/source/cuopt-server/nim-operator/guide/cuopt-nimservice-full.yaml, docs/cuopt/source/cuopt-server/nim-operator/guide/cuopt-nimservice.yaml, docs/cuopt/source/cuopt-server/nim-operator/guide/deploy.sh, regression/config.sh	NIM operator YAML manifests, deployment script, and regression test configuration updated to use new versioned image tags (26.6.0-cu12 for stable, 26.6.0a-cu12 for nightly).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Suggested labels

doc, non-breaking

Suggested reviewers

• tmckayus

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding short Docker tag aliases (cu12/cu13) and updating documentation to use them.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of publishing short Docker tag aliases and updating documentation files.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/simplify-docker-image-tags

---

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

[coderabbitai]

🧹 Nitpick comments (1)

README.md (1)

139-141: ⚡ Quick win

Consider clarifying Python version selection for short tags.

The documentation explains the new simplified tags but doesn't specify which Python version the short tags (e.g., latest-cu12, 26.6.0-cu12) correspond to when multiple Python versions are supported. Users may need to know whether latest-cu12 uses Python 3.13, 3.14, or the latest supported version.

Consider adding a sentence like: "Short tags use the latest supported Python version for that release" or similar guidance.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 139 - 141, Clarify which Python version short Docker
tags map to by adding a sentence in the README where you describe short tags
(references: "latest", "<version>-cu12", "<version>-cu13", and examples like
"26.6.0-cu12"); state that short tags implicitly use the latest supported Python
minor for that CUDA/release (e.g., "Short tags use the latest supported Python
version for that release") and optionally add a note pointing readers to the
fully-qualified tags (e.g., "26.6.0-cuda12.9-py3.14") if they need to pin a
specific Python version.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@README.md`:
- Around line 139-141: Clarify which Python version short Docker tags map to by
adding a sentence in the README where you describe short tags (references:
"latest", "<version>-cu12", "<version>-cu13", and examples like "26.6.0-cu12");
state that short tags implicitly use the latest supported Python minor for that
CUDA/release (e.g., "Short tags use the latest supported Python version for that
release") and optionally add a note pointing readers to the fully-qualified tags
(e.g., "26.6.0-cuda12.9-py3.14") if they need to pin a specific Python version.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0f0aab88-406d-4e9e-ad46-d557fe362748

📥 Commits

Reviewing files that changed from the base of the PR and between c4e878d and b9e4eb6.

📒 Files selected for processing (9)

• README.md
• ci/docker/create_multiarch_manifest.sh
• docs/cuopt/source/_static/install-selector.js
• docs/cuopt/source/cuopt-grpc/advanced.rst
• docs/cuopt/source/cuopt-server/nim-operator/configuration.rst
• docs/cuopt/source/cuopt-server/nim-operator/guide/cuopt-nimservice-full.yaml
• docs/cuopt/source/cuopt-server/nim-operator/guide/cuopt-nimservice.yaml
• docs/cuopt/source/cuopt-server/nim-operator/guide/deploy.sh
• regression/config.sh

[github-actions]

🔔 Hi @anandhkb @rgsl888prabhu, this pull request has had no activity for 7 days. Please update or let us know if it can be closed. Thank you!

If this is an "epic" issue, then please add the "epic" label to this issue.
If it is a PR and not ready for review, then please convert this to draft.
If you just want to switch off this notification, then use the "skip inactivity reminder" label.

[github-actions]

🔔 Hi @anandhkb @rgsl888prabhu, this pull request has had no activity for 7 days. Please update or let us know if it can be closed. Thank you!

If this is an "epic" issue, then please add the "epic" label to this issue.
If it is a PR and not ready for review, then please convert this to draft.
If you just want to switch off this notification, then use the "skip inactivity reminder" label.