Update redirect for latest server version 26.0

[stktung]

Description

Page previews

[qodo-code-review]

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

Review Summary by Qodo

Update latest server redirect to version 26.0

✨ Enhancement

Walkthroughs

Description

• Update latest server version redirect from v25.1 to v26.0
• Ensures users accessing latest documentation receive v26.0 content

Diagram

flowchart LR
  A["User requests /server/latest/*"] -- "301 redirect" --> B["v25.1/:splat (old)"]
  C["User requests /server/latest/*"] -- "301 redirect" --> D["v26.0/:splat (new)"]

Loading

File Changes

1. docs/.vuepress/public/_redirects ⚙️ Configuration changes +1/-1

Update latest version redirect target

• Updated redirect rule for /server/latest/* to point to v26.0 instead of v25.1
• Single line change in the 'latest to latest' section of redirect configuration

docs/.vuepress/public/_redirects

---

[github-actions]

Docs build

• Status: ✅ Build succeeded
• Preview: https://fix-redirect-latest-to-26.documentation-21k.pages.dev
  Changed pages:

[cloudflare-workers-and-pages]

Deploying documentation with    Cloudflare Pages

Latest commit:	630bfd7
Status:	✅  Deploy successful!
Preview URL:	https://b280cc5f.documentation-21k.pages.dev
Branch Preview URL:	https://fix-redirect-latest-to-26.documentation-21k.pages.dev

View logs

[github-actions]

Docs build

• Status: ✅ Build succeeded
• Preview: https://fix-redirect-latest-to-26.documentation-21k.pages.dev
  Changed pages:

[qodo-code-review]

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Homepage links to v25.0 🐞 Bug ✓ Correctness

Description

• The PR moves /server/latest/* to /server/v26.0/*, but the docs homepage still hard-codes
  several key entry links to /server/v25.0/....
• v25.0 is marked deprecated/hidden in the import configuration, so promoting it from the homepage
  conflicts with the versioning intent and will keep routing users to older docs.
• This creates a recurring release-maintenance hazard: updating “latest” in redirects without
  updating homepage entry points leaves the site inconsistent.

Code

docs/.vuepress/public/_redirects[254]

+/server/latest/*                            /server/v26.0/:splat                     301

Evidence

The redirect change makes /server/latest/* resolve to v26.0, but the homepage still sends users to
v25.0. Additionally, the import configuration explicitly marks v25.0 as deprecated/hidden while
listing v26.0 first (which the versioning logic treats as latest).

docs/.vuepress/public/_redirects[241-255]
docs/README.md[106-129]
import/repos.json[10-31]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs homepage (`docs/README.md`) hard-codes links to `/server/v25.0/...` (HTTP API, Connectors, Admin UI). After this PR, `/server/latest/*` redirects to `/server/v26.0/*`, and `v25.0` is marked deprecated/hidden in `import/repos.json`, so the homepage will continue sending users to an older/deprecated version.

## Issue Context
- Redirects: `/server/latest/*` now points to `/server/v26.0/:splat`.
- Import/version config: `v25.0` is `deprecated: true` and `hide: true`.
- The homepage is a high-traffic entrypoint; keeping it on v25.0 undermines the release bump.

## Fix Focus Areas
- docs/README.md[106-129]
- import/repos.json[10-31]
- docs/.vuepress/public/_redirects[253-255]

## Suggested change
- Replace `/server/v25.0/...` links in `docs/README.md` with `/server/v26.0/...` equivalents.
- (Optional, more robust) Add a client-side redirect route for deep paths:
 - In `docs/.vuepress/client.ts`, add something like:
   - `addDynamicRoute('/server/latest/:pathMatch(.*)*', to => to.path.replace(/^\/server\/latest/, `/${__VERSIONS__.latest}`));`
 - Then you could safely use `/server/latest/...` links throughout the site without relying on the hosting redirects during SPA navigation.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more