HyukjinKwon opened a new pull request, #57269:
URL: https://github.com/apache/spark/pull/57269

   ### What changes were proposed in this pull request?
   
   This PR adds a step to the `finalize` phase of 
`dev/create-release/release-build.sh` that updates two spark-website source 
files that were previously edited by hand:
   
   - `downloads.md`: bump the Maven coordinate example (`version:`) to the 
latest stable release.
   - `site/static/versions.json`: add an entry for the new release, keeping the 
list sorted in descending version order.
   
   `site/downloads.html` is intentionally not edited here because it is 
regenerated from `downloads.md` by the existing `bundle exec jekyll build` step.
   
   Both updates are guarded by the same `-preview` check used by the 
neighboring steps, so preview releases are not affected.
   
   ### Why are the changes needed?
   
   The release automation already updates most of the spark-website 
(`documentation.md`, `js/downloads.js`, the news post, the JIRA release notes, 
the docs, and the `latest` symlink), but it did not touch `downloads.md` or 
`site/static/versions.json`. As a result the release manager had to create 
these edits manually, e.g. https://github.com/apache/spark-website/pull/701.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. This only affects the release tooling.
   
   ### How was this patch tested?
   
   Extracted the new block from the script and ran it locally against realistic 
spark-website fixtures across many scenarios:
   
   - Feature release (newest) updates both files and reproduces the manual 
[spark-website#701](https://github.com/apache/spark-website/pull/701) diff.
   - Preview releases (`-preview1`, `-preview2`) skip both files, matching the 
sibling steps.
   - Old-branch maintenance releases insert into the correct sorted slot in 
`versions.json` and never downgrade the `downloads.md` coordinate.
   - `downloads.md` is only bumped when the release is strictly newer than what 
is shown.
   - `versions.json` keeps every patch entry and is idempotent / dedup-safe on 
re-runs.
   - Output remains valid JSON with the existing `indent=4` formatting and 
trailing newline.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.8)


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