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

   Move every Apache Doris download link off `download.velodb.io` and onto
   `https://apache-doris-releases.oss-accelerate.aliyuncs.com/` — first on the
   download page itself, then in the `current` and 4.x doc trees.
   
   ## Versions
   
   - [x] dev
   - [x] 4.x
   - [ ] 3.x
   - [ ] 2.1 or older (not covered by version/language sync gate)
   
   ## Languages
   
   - [x] Chinese
   - [x] English
   - [ ] Japanese candidate translation needed
   
   ## Docs Checklist
   
   - [x] Checked by AI
   - [ ] Test Cases Built
   - [x] Updated required version and language counterparts, or explained why 
not
   - [x] If only one language changed, confirmed whether source/translation 
counterparts need sync
   
   ## Download page
   
   `src/constant/download.data.ts`
   
   - `ORIGIN` now points at the OSS bucket, which covers all 670 `${ORIGIN}...`
     links — tarballs, `.asc` and `.sha512` alike.
   - The twelve Doris Streamloader links were hardcoded to the old host. They 
now
     use `${ORIGIN}` like everything else in the file, so the next host change 
is
     a one-line edit.
   - The whole 2.0.3 entry is dropped from `ALL_VERSIONS`. Its no-avx2 artifacts
     have been 404 on every host this page has used — aliyuncs, velodb and
     selectdb — and Apache only archives source for that release, so there is
     nothing to point the row at.
   
   Source packages (`dist`/`archive.apache.org`), the Kafka / Flink / Spark
   connectors (`downloads` and `repository.apache.org`, Maven Central) and Doris
   Operator are untouched — they never used this host.
   
   `doc-tools/skills/add-release/scripts/validate-release.{mjs,test.mjs}` — the
   release validator asserts that `ORIGIN` matches its `binaryOrigin`, so its
   default and fixtures move with it. Without this the next release would fail
   validation.
   
   ## Docs
   
   Twelve files, sixteen occurrences, three distinct artifacts — the Filebeat 
and
   Fluent Bit builds and the Logstash output plugin gem — on the Beats, Fluent 
Bit
   and log-analysis pages, in English and Chinese, for both `current` and 4.x.
   These live under `extension/` and `integrations/` rather than the bucket 
root,
   so the paths were confirmed on the new host before the swap.
   
   ## Verification
   
   Every link was checked, not sampled.
   
   **Download page** — the edited module was transpiled and evaluated, and every
   URL it renders was probed:
   
   | | before | after |
   |---|---|---|
   | file links | 535 | 526 |
   | HTTP 200 | 532 | **526** |
   | 404 | 3 (the 2.0.3 no-avx2 trio) | **0** |
   
   Cross-checked against the old host as well: all 532 live artifacts matched on
   both status and `Content-Length`, and the 350 `.asc` / `.sha512` files were
   byte-identical across the two hosts.
   
   **Docs** — all three artifacts resolve with a `Content-Length` identical to 
the
   old host:
   
   ```
   200  101723712  extension/filebeat-doris-2.1.1
   200   45834456  integrations/fluent-bit-doris-3.1.9
   200      10752  extension/logstash-output-doris-1.2.0.gem
   ```
   
   `docs:links:changed` reports `errors=false`, and `docs:i18n-sync:changed`
   reports info-level findings only.
   
   ## Left for a separate change
   
   - The 3.x, 2.1, 2.0 and 1.2 doc trees still point at `download.velodb.io`
     (62 occurrences), as do three files under `community/`.
   - The Japanese tree was never migrated off `download.selectdb.com`, so it 
does
     not match this PR's search and is untouched. Its links still resolve. Since
     this PR only rewrites URLs and adds no prose, no Japanese translation
     candidate is needed — the Japanese pages need their own host swap instead.
   
   🤖 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