Is it guaranteed that the rust release associated with a given Github release is available immediately when the github release is published? That is, is the Github release published after or simultaneously with the release being made available on releases.rs and rustup?
FYI, releases.rs itself is an unofficial website, not part of the Rust project, and unrelated to the actual release process. Of course, it’s a very useful website a community member kindly created on GitHub, which helps to get a good overview about release notes of former releases, and ongoing work on future releases; but if they don’t want to keep it up anymore, it might disappear or fall out of date.
The question of the order of publishing of the Rust release available through rustup vs. tags and/or release-notes appearing on GitHub is a different one, and I don’t know the exact answer to that one.
It looks like I’ve found the relevant part of the release script
here seem to be the uploads for rustup etc, so the release actually exists and is usable afterwards:
And then only afterwards, here it creates the blog post and the tag on GitHub
so it looks like the answer to your question is: yes[1] it’s guaranteed that the tag, and subsequently also the Release on GitHub only happens after the release is actually available.
at least at the moment
I don’t see however any good reason why this should ever change in the future – who would want to publish release announcements before the release is usable? E.g., what if the release publishing fails, but it’s already announced?↩︎
Thanks for digging! And thanks for the note about releases.rs. A little more digging pointed me to the default distribution server, https://static.rust-lang.org