Repository navigation
1.72.1 is not released on GitHub #115976
Copy link
Copy link
Closed
Labels
T-releaseRelevant to the release subteam, which will review and decide on the PR/issue.Relevant to the release subteam, which will review and decide on the PR/issue.
Description
Activity
- addedneeds-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triagingThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
on Sep 19, 2023 I suspect we need to copy the release notes to master.
Reacted by sksat@Mark-Simulacrum I tried to respond with #115978, is this what you meant?
- addedT-releaseRelevant to the release subteam, which will review and decide on the PR/issue.Relevant to the release subteam, which will review and decide on the PR/issue.and removedneeds-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triagingThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
on Sep 19, 2023 - added a commit that references this issue
on Sep 20, 2023 - Reacted by sksat
@fmease: Why is the release not marked as
latest? What is the authoritative source of thelatestversion?Good catch! At the moment, 1.71.1 is flagged as
latestpresumably since the release notes for 1.71.1 (#115997) were merged several hours after the ones for 1.72.1 (#115978).I'm not a T-release member and I'm not super familiar with GitHub releases.
@Mark-Simulacrum, is there a simple way to mark 1.72.1 aslatest?Should be fixed.
Reacted by León Orell Valerian Liehr, Frederik Rothenberger and sksat
Metadata
Metadata
Assignees
Labels
T-releaseRelevant to the release subteam, which will review and decide on the PR/issue.Relevant to the release subteam, which will review and decide on the PR/issue.
The 1.72.1 release was announced: https://blog.rust-lang.org/2023/09/19/Rust-1.72.1.html
Actually, this tag exists: https://github.com/rust-lang/rust/releases/tag/1.72.1
However, this version does not seem to exist in GitHub Releases: https://github.com/rust-lang/rust/releases
It seems that this operation is usually done by a bot, so is there some problem with the automated release procedure?