Update the docs base to use the v2.15 once available

[mantis-toboggan-md]

Links to Rancher documentation use a base url, docsBase, which includes a version number. The version number is hardcoded. When 2.15 docs become available, we need to update the value here: https://github.com/rancher/dashboard/blob/master/shell/config/version.js#L33

[github-actions]

🎯 Agentic Issue Triage

Summary: This is a maintenance task to update the hardcoded Rancher documentation base URL version from v2.13 to v2.15 once the v2.15 docs are published. This ensures in-app documentation links point to the correct version.

📍 Code Location & Context

The version is defined in two places working together:

1. shell/config/version.js (line 33):

   export const CURRENT_RANCHER_VERSION = '2.13';

2. shell/config/private-label.js (line 8):

   export const DOCS_BASE = `(ranchermanager.docs.rancher.com/redacted) CURRENT_RANCHER_VERSION }`;

3. shell/store/i18n.js consumes DOCS_BASE and injects it as docsBase into i18n translations, which are used throughout the app for doc links.

The fix is a one-liner: update CURRENT_RANCHER_VERSION from '2.13' to '2.15' — but only once the v2.15 docs are live at `(ranchermanager.docs.rancher.com/redacted)

✅ Checklist

• Verify that `(ranchermanager.docs.rancher.com/redacted) is live and contains the expected content
• Update CURRENT_RANCHER_VERSION in shell/config/version.js from '2.13' to '2.15'
• Smoke-test a few in-app doc links to confirm they resolve correctly
• Check if any other places hardcode a Rancher version string for docs (run: grep -rn 'v2\.\(13\|14\)' shell/config/)

💡 Notes & Nudges

• This issue is milestoned for v2.15.0 — the update should land before or alongside the v2.15 release.
• Consider whether CURRENT_RANCHER_VERSION could be made dynamic (derived from the running Rancher server's version API) to avoid needing this manual update in the future. The getVersionData() function in shell/config/version.js already retrieves the live version from /rancherversion — it may be possible to derive DOCS_BASE from that at runtime.
• Useful resource: [Rancher Docs site]((ranchermanager.docs.rancher.com/redacted) — check when v2.15 path goes live.

Generated by Agentic Triage for issue #17667 · ● 261.6K · ◷

[mantis-toboggan-md]

The check-i18n-links workflow should validate that all Rancher documentation links still return 200 or 202.

[github-actions]

🤖 Issue grooming questions

Thanks for filing this! The technical pointer (specific file and line) is helpful. A couple of things are needed before this can move to triage:

1. Missing: Acceptance Criteria

Please add a concrete, testable checklist of what "done" looks like. For example:

• docsBase in shell/config/version.js is updated to point to the v2.15 documentation URL once the v2.15 docs are published.
• All translation strings using docsBase correctly resolve to v2.15 documentation pages in a Rancher 2.15 build.

2. Missing: User-facing impact / flow

Could you briefly describe which UI surfaces are affected by this stale version string? (e.g. "the documentation link in the cluster edit banner, the RKE2 provisioning form, and any other places docsBase is used") — this helps scope the validation effort.

This comment was generated automatically to help gather the information needed to groom this issue.

Generated by Daily Issue Grooming · ● 370.5K · ◷