ashwin-sampathkumar opened a new pull request, #41397:
URL: https://github.com/apache/beam/pull/41397

   ### Description
   
   Fixes broken `[download page]` links on Apache Beam GitHub Releases (such as 
`v2.78.0-RC4`, `v2.77.0`, and earlier releases).
   
   #### Why this happens
   In `contributor-docs/release-guide.md`, the release blog post template uses 
a root-relative path:
   ```markdown
   See the [download page](/get-started/downloads/{$DOWNLOAD_ANCHOR}) for this 
release.
   ```
   Since #32576 updated the release process to copy the blog post content 
directly into the GitHub Release description (instead of using 
`.github/workflows/publish_github_release_notes.yml`, which rewrote `](/` to 
`](https://beam.apache.org/`), `/get-started/downloads/...` resolves against 
`https://github.com` (`https://github.com/get-started/downloads/...`) and 
returns a 404 on GitHub Releases. In addition, unresolved RC date placeholders 
(e.g., `#2780-2026-11-??`) can persist into finalized GitHub Releases if the 
release description is not refreshed when publishing the final tag.
   
   #### Changes
   - Use the absolute 
`https://beam.apache.org/get-started/downloads/{$DOWNLOAD_ANCHOR}` URL in the 
release blog post template so it works both on `beam.apache.org` and when 
copied into GitHub Releases.
   - Clarify in **Update the Github Release with the Blog post content** that 
Beam website links must use absolute `https://beam.apache.org/...` URLs and 
should not include unresolved `#...-??` placeholders during the RC phase.
   - Add a step in **Publish the Github Release page** to update the GitHub 
Release description from the finalized blog post once the final release date 
anchor is known.
   - Fix two remaining root-relative `/get-started/downloads/` links in 
`contributor-docs/release-guide.md` itself.
   


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