Improve description of `catalog.cattle.io/ui-extensions-version` in docs

[aalves08]

Is your feature request related to a problem? Please describe.

Improve description of catalog.cattle.io/ui-extensions-version in docs https://extensions.rancher.io/extensions/next/configuration so that developers know what it does exactly and what it compares to

Describe the solution you'd like

Describe alternatives you've considered

Additional context

[github-actions]

🎯 Agentic Issue Triage

This is a documentation enhancement request to improve the description of the catalog.cattle.io/ui-extensions-version annotation in the Rancher UI Extensions configuration docs, so developers better understand what the annotation does and what it compares against at runtime.

📋 Issue Summary

Type: Documentation improvement / Enhancement
Area: UI Extensions (area/extensions, area/documentation)
Milestone: v2.15.0
Priority: 2 (normal)

The current documentation at (extensions.rancher.io/redacted) lacks a clear explanation of:

• What catalog.cattle.io/ui-extensions-version actually does at runtime
• What value it is compared against (e.g. the installed UI Extensions plugin version, the Rancher version, or some other version source)
• What happens when the version constraint is not satisfied (extension hidden? error?)

🔍 Relevant Code & Context

• The annotation catalog.cattle.io/ui-extensions-version is likely a semver range annotation on a Helm chart / extension package that the UI extensions loader evaluates.
• Relevant source to investigate:
  • pkg/ directory — any extension loading/validation logic
  • shell/ — any catalog or extension-version-checking logic (e.g. search for ui-extensions-version in shell/)
  • The docusaurus source at docusaurus/ for the configuration page that needs updating

Quick grep to find existing usages:

grep -r "ui-extensions-version" shell/ pkg/ docusaurus/ --include="*.ts" --include="*.js" --include="*.vue" --include="*.md" -l

✅ Suggested Sub-tasks

• Locate where catalog.cattle.io/ui-extensions-version is read and evaluated in the codebase
• Determine what value/version it is compared against (shell plugin API version? Rancher version?)
• Document the comparison logic and the effect when the constraint is not met
• Update docusaurus/ configuration docs page with:
  • A clear description of the annotation's purpose
  • The format expected (semver range)
  • What it is compared to
  • Behaviour when the constraint fails
• Optionally add an example showing valid semver range values

💡 Notes & Resources

• [Rancher UI Extensions – Configuration Docs (next)]((extensions.rancher.io/redacted)
• SemVer ranges (npm semver) – likely the format used
• If the annotation gates extension loading based on the UI plugin API/SDK version, this is important to communicate clearly to extension authors so they can set appropriate constraints.

Note

🔒 Integrity filter blocked 1 item

The following item were blocked because they don't meet the GitHub integrity level.

• #13862 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Agentic Triage for issue #17510 · ● 136.2K · ◷