[Docs] Improve manual-download.html phrasing. (#11084)

Emphasize that SDK version 1.4.0 was the latest at the time
of writing instructions, and is outdated now.

changelog_begin
changelog_end
This commit is contained in:
Artúr Poór 2021-10-11 08:40:50 +02:00 committed by GitHub
parent 9b2a8c7eb5
commit 0f265fd715
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -11,7 +11,7 @@ Note that the Windows installer is already signed (within the binary itself), an
To do that: To do that:
1. Go to https://github.com/digital-asset/daml/releases. Confirm your browser sees a valid certificate for the github.com domain. 1. Go to https://github.com/digital-asset/daml/releases. Confirm your browser sees a valid certificate for the github.com domain.
2. Download the artifact (*Assets* section, after the release notes) for your platform as well as the corresponding signature file. For example, if you are on macOS and want to install release 1.4.0, you would download the files ``daml-sdk-1.4.0-macos.tar.gz`` and ``daml-sdk-1.4.0-macos.tar.gz.asc``. Note that for Windows you can choose between the tarball (ends in ``.tar.gz``), which follows the same instructions as the Linux and macOS ones (but assumes you have a number of typical Unix tools installed), or the installer, which ends with ``.exe``. Regardless, the steps to verify the signature are the same. 2. Download the artifact (*Assets* section, after the release notes) for your platform as well as the corresponding signature file. For example, if you are on macOS and want to install the latest release (1.4.0 at the time of writing), you would download the files ``daml-sdk-1.4.0-macos.tar.gz`` and ``daml-sdk-1.4.0-macos.tar.gz.asc``. Note that for Windows you can choose between the tarball (ends in ``.tar.gz``), which follows the same instructions as the Linux and macOS ones (but assumes you have a number of typical Unix tools installed), or the installer, which ends with ``.exe``. Regardless, the steps to verify the signature are the same.
3. To verify the signature, you need to have ``gpg`` installed (see 3. To verify the signature, you need to have ``gpg`` installed (see
https://gnupg.org for more information on that) and the Digital Asset https://gnupg.org for more information on that) and the Digital Asset
Security Public Key imported into your keychain. Once you have ``gpg`` Security Public Key imported into your keychain. Once you have ``gpg``