Skip to content

[DB-2056] Add branch v26.1 to repos.json#962

Merged
stktung merged 1 commit intomasterfrom
26.1
Apr 30, 2026
Merged

[DB-2056] Add branch v26.1 to repos.json#962
stktung merged 1 commit intomasterfrom
26.1

Conversation

@timothycoleman
Copy link
Copy Markdown
Contributor

Added new branch version v26.1 to repos.json.

Description

Page previews

Added new branch version v26.1 to repos.json.
@timothycoleman timothycoleman requested a review from a team as a code owner April 30, 2026 10:50
@timothycoleman timothycoleman changed the title Add branch v26.1 to repos.json [DB-2056] Add branch v26.1 to repos.json Apr 30, 2026
@qodo-code-review
Copy link
Copy Markdown
Contributor

qodo-code-review Bot commented Apr 30, 2026

Review Summary by Qodo

(Agentic_describe updated until commit c60d74d)

Add v26.1 branch configuration to repos.json

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Add v26.1 branch configuration to repos.json
• New branch includes version, name, path, and start page
Diagram
flowchart LR
  repos["repos.json"] -- "add v26.1 branch" --> config["v26.1 branch config"]
  config -- "version: v26.1" --> version["Version"]
  config -- "name: release/v26.1" --> name["Branch Name"]
  config -- "relativePath: server" --> path["Relative Path"]
  config -- "startPage: quick-start/" --> start["Start Page"]
Loading

Grey Divider

File Changes

1. import/repos.json ⚙️ Configuration changes +6/-0

Add v26.1 branch configuration entry

• Added new v26.1 branch entry to the branches array
• Configured with version "v26.1", branch name "release/v26.1"
• Set relative path to ["server"] and start page to "quick-start/"
• Positioned as the first branch entry before v26.0

import/repos.json


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown
Contributor

qodo-code-review Bot commented Apr 30, 2026

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

Grey Divider


Action required

1. Latest redirect points old 🐞 Bug ≡ Correctness
Description
By inserting v26.1 before v26.0 in import/repos.json, the import pipeline and Versioning.latest
will treat v26.1 as the latest stable version, but Cloudflare Pages still redirects
/server/latest/* to /server/v26.0/*, serving the wrong docs for “latest” URLs.
Code

import/repos.json[R11-16]

+      {
+        "version": "v26.1",
+        "name": "release/v26.1",
+        "relativePath": ["server"],
+        "startPage": "quick-start/"
+      },
Evidence
The import script preserves the branches ordering when generating the server versions list, and
Versioning.latest picks the first non-preview server version as the latest. With v26.1 now first,
the app’s latest becomes v26.1, but _redirects still forces /server/latest/* to v26.0,
overriding the app routing at the edge.

import/repos.json[11-16]
import/import.cjs[105-111]
docs/.vuepress/lib/versioning.ts[63-71]
docs/.vuepress/public/_redirects[253-255]
docs/.vuepress/config.ts[32-37]

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

### Issue description
Adding `v26.1` as the newest server branch makes it the computed latest version, but Cloudflare Pages redirects still hardcode `/server/latest/*` to `/server/v26.0/:splat`, so users hitting “latest” URLs are redirected to the wrong (older) docs.

### Issue Context
- `import/import.cjs` generates `generated-versions.json` in the same order as `repo.branches`.
- `docs/.vuepress/lib/versioning.ts` defines `latest` as the first non-preview server version.
- `_redirects` is evaluated by Cloudflare Pages before client-side routing.

### Fix Focus Areas
- docs/.vuepress/public/_redirects[253-255]

### What to change
- Update the `/server/latest/*` redirect target from `/server/v26.0/:splat` to `/server/v26.1/:splat` (and ensure any related “latest” redirect rules remain consistent).

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


Grey Divider

Previous review results

Review updated until commit c60d74d

Results up to commit c60d74d


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


Action required
1. Latest redirect points old 🐞 Bug ≡ Correctness
Description
By inserting v26.1 before v26.0 in import/repos.json, the import pipeline and Versioning.latest
will treat v26.1 as the latest stable version, but Cloudflare Pages still redirects
/server/latest/* to /server/v26.0/*, serving the wrong docs for “latest” URLs.
Code

import/repos.json[R11-16]

+      {
+        "version": "v26.1",
+        "name": "release/v26.1",
+        "relativePath": ["server"],
+        "startPage": "quick-start/"
+      },
Evidence
The import script preserves the branches ordering when generating the server versions list, and
Versioning.latest picks the first non-preview server version as the latest. With v26.1 now first,
the app’s latest becomes v26.1, but _redirects still forces /server/latest/* to v26.0,
overriding the app routing at the edge.

import/repos.json[11-16]
import/import.cjs[105-111]
docs/.vuepress/lib/versioning.ts[63-71]
docs/.vuepress/public/_redirects[253-255]
docs/.vuepress/config.ts[32-37]

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

### Issue description
Adding `v26.1` as the newest server branch makes it the computed latest version, but Cloudflare Pages redirects still hardcode `/server/latest/*` to `/server/v26.0/:splat`, so users hitting “latest” URLs are redirected to the wrong (older) docs.

### Issue Context
- `import/import.cjs` generates `generated-versions.json` in the same order as `repo.branches`.
- `docs/.vuepress/lib/versioning.ts` defines `latest` as the first non-preview server version.
- `_redirects` is evaluated by Cloudflare Pages before client-side routing.

### Fix Focus Areas
- docs/.vuepress/public/_redirects[253-255]

### What to change
- Update the `/server/latest/*` redirect target from `/server/v26.0/:splat` to `/server/v26.1/:splat` (and ensure any related “latest” redirect rules remain consistent).

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


Qodo Logo

@linear
Copy link
Copy Markdown

linear Bot commented Apr 30, 2026

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented Apr 30, 2026

Deploying documentation with  Cloudflare Pages  Cloudflare Pages

Latest commit: c60d74d
Status: ✅  Deploy successful!
Preview URL: https://329acdde.documentation-21k.pages.dev
Branch Preview URL: https://26-1.documentation-21k.pages.dev

View logs

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 30, 2026

Docs build

@github-actions
Copy link
Copy Markdown

Docs build

Comment thread import/repos.json
Comment on lines +11 to +16
{
"version": "v26.1",
"name": "release/v26.1",
"relativePath": ["server"],
"startPage": "quick-start/"
},
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Latest redirect points old 🐞 Bug ≡ Correctness

By inserting v26.1 before v26.0 in import/repos.json, the import pipeline and Versioning.latest
will treat v26.1 as the latest stable version, but Cloudflare Pages still redirects
/server/latest/* to /server/v26.0/*, serving the wrong docs for “latest” URLs.
Agent Prompt
### Issue description
Adding `v26.1` as the newest server branch makes it the computed latest version, but Cloudflare Pages redirects still hardcode `/server/latest/*` to `/server/v26.0/:splat`, so users hitting “latest” URLs are redirected to the wrong (older) docs.

### Issue Context
- `import/import.cjs` generates `generated-versions.json` in the same order as `repo.branches`.
- `docs/.vuepress/lib/versioning.ts` defines `latest` as the first non-preview server version.
- `_redirects` is evaluated by Cloudflare Pages before client-side routing.

### Fix Focus Areas
- docs/.vuepress/public/_redirects[253-255]

### What to change
- Update the `/server/latest/*` redirect target from `/server/v26.0/:splat` to `/server/v26.1/:splat` (and ensure any related “latest” redirect rules remain consistent).

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

@qodo-code-review
Copy link
Copy Markdown
Contributor

qodo-code-review Bot commented Apr 30, 2026

Persistent review updated to latest commit c60d74d

@github-actions
Copy link
Copy Markdown

Docs Preview

  • Status: ⏳ Creating preview…

@github-actions
Copy link
Copy Markdown

Docs build

@stktung stktung merged commit 617daa0 into master Apr 30, 2026
5 checks passed
@stktung stktung deleted the 26.1 branch April 30, 2026 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants