morningman opened a new pull request, #4155:
URL: https://github.com/apache/doris-website/pull/4155

   ## Summary
   
   Take Apache Doris 4.1.4 off `/download/` and `/releases/`. This reverses 
#4128 (the arm64 row had already been withdrawn in #4133).
   
   - `src/constant/download.data.ts`: drop the 4.1.4 entry from `ALL_VERSIONS`. 
`ACTIVE_CORE_BRANCHES` is unchanged; `ACTIVE_HEADS` now offers 4.1.3 as 
**Latest** on the quick download card again.
   - `releasenotes/core.md` + zh-CN mirror: restore the 4.1.3 Latest tip and 
remove the `2026-09-10` chronological entry.
   - `sidebarsReleases.json`: remove `v4.1/release-4.1.4`.
   - Delete `releasenotes/v4.1/release-4.1.4.md` and its zh-CN twin, so 
`/releases/v4.1/release-4.1.4` is no longer built.
   
   The release notes stay recoverable from git history (`git show 
0e05e562bd:releasenotes/v4.1/release-4.1.4.md`) if 4.1.4 is re-published later.
   
   ## Validation
   
   - `node --test 
doc-tools/skills/add-release/scripts/validate-release.test.mjs` — 6/6 passed
   - `validate-release.mjs --component doris-core --version 4.1.3 --series 4.1 
--source-version 4.1.3-rc02 --release-date 2026-07-13 --position latest` — 65 
checks passed (4.1.3 is the newest patch of 4.1 again; all twelve 4.1.3 
artifact URLs reachable)
   - `sidebarsReleases.json` JSON parse check
   - No remaining `release-4.1.4` / `4.1.4-rc04` references anywhere in the 
repo (no dangling links)
   - `git diff --check` — clean
   
   `yarn build` / `yarn typecheck` were not run.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to