Looking for the "latest" alias/symlink to automatically grab the latest
version? If so, then you are in the right place.

While there is no "latest" symlink, there is the toolchain.sha256 file
next to this README that serves the same purpose while providing a few
extra benefits. Specifically, it always contains paths (relative to its
location) to the latest toolchain source files plus their SHA256 checksums
(the format of that file is the same as what's expected by the sha256sum
utility from Linux coreutils).

Using this file over the "latest" symlink has several benefits:

1. It includes SHA256 checksums of all the toolchain files which are
   easy to verify with sha256sum (there is also the easy to extract
   version as the first line comment).

2. Because the toolchain consists of multiple files, with the symlink
   approach it is possible to end up with files from different toolchains
   if you happen to download the files as the symlink is being switched
   to the new version.

   In contrast, if you first download the toolchain.sha256 file, then
   download the files it lists, and verify their checksums, then you can
   be reasonably certain you have downloaded a correct and consistent
   set of files.

The toolchain.sha256 is guaranteed to be always present and pointing to
the latest stable toolchain version. Its format will not change except
for adding new lines describing additional files.

Note that there is also toolchain-bindist.sha256 next to toolchain.sha256,
which serves the same purpose but for binary packages.