Aditya Telange

Hello @rom1v, "This script is always intended to be executed on the master branch as a convenience to install the latest release" please consider tagging it to releases or tags....

I knew you'd come to this as from the way I mentioned, the binary will be safe from tampering but not checksusms.txt is not. And this is a never ending...

I am not sure how the release takes place, or maintainers directly drag and drop binaries as assets in a release. Proposing following method, let me know if I can...

> I'm blind. Can't see where $GIT_CLONED_VERSION variable defined! Try developing an ability to correlate that it is a typo for `GIT_TAG_VERSION`

> Sorry, there is no way the script will download and accept a file that can be replaced on the remote server in the future. So you have trust issues...

Its a warning, chill WARN deprecated: .Site.Social was deprecated in Hugo v0.124.0 and will be removed in a future release. Use .Site.Params instead.

> @adityatelange > > Prior to v0.136.0 this emits a warning. With v0.136.0 and later this emits an error and fails the build. Finding difficult to keep up with Hugo'a...

Upstream patches from Hugo and @jpmcb for templates are pushed. This should fix the issue.