arnavsharma990 opened a new pull request, #186:
URL: https://github.com/apache/nuttx-website/pull/186

   ## Summary
   
   The SHA-512 and Signature columns on the download page were built from 
`release.artifact-root`, so for every mirror-served release they pointed at the 
`dyn/closer.lua` mirror selector and returned an HTML mirror-selection page 
instead of the file. Every release file already defines `checksum-root` for 
exactly this purpose, but no template read it. This PR switches the two columns 
to `release.checksum-root` and leaves the Archive column on 
`release.artifact-root`.
   
   Fixes #185.
   
   ## Changes
   
   - `download.md:51-52`: `.sha512` / `.asc` hrefs now use 
`{{release.checksum-root}}` instead of `{{release.artifact-root}}`. Two lines, 
no other page changes.
   
   ## Verification
   
   - `curl` before: 
`.../dyn/closer.lua/nuttx/12.12.0/apache-nuttx-12.12.0.tar.gz.sha512` → `200 
text/html`, ~21 KB mirror-picker page.
   - `curl` after (canonical form now generated): 
`https://downloads.apache.org/nuttx/12.12.0/apache-nuttx-12.12.0.tar.gz.sha512` 
→ `200 text/plain`, 158 bytes (the hash); `.asc` → `200 text/plain`, 833-byte 
PGP signature.
   - Simulated the Liquid output for all 27 Apache releases: generated URLs 
resolve under each release's `checksum-root` (e.g. 
`.../incubator/nuttx/10.1.0/...`, `.../nuttx/13.0.1/...`).
   - Archive rows (9.0.0, 9.1.0, 10.0.0) have `checksum-root == artifact-root`, 
so their links are byte-identical before/after — no special handling needed. 
Legacy non-Apache table untouched (no hash/signature columns).
   
   ## Backwards compatibility
   
   Link targets change from mirror-picker pages to canonical files; the old 
closer.lua URLs remain valid for anyone who bookmarked them. No permalink, 
collection, or deployment changes.


-- 
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]

Reply via email to