Checksum of the download script
Following up on #449. Having the checksum of the install script published somewhere (not sure where, though) would also be very convenient.
Does the install script mean the download script? Could you explain your use case?
Yes, the download script, thank you.
I am writing a custom Gitea Actions workflow and cannot use any existing actionlint GitHub actions, since they depend on the GitHub status check API and require a GITHUB_TOKEN passed in.
Now that I think about it, I still have to verify the checksum of the binary the script downloads. And I need to select the correct checksum based on the current runner architecture. I wanted to avoid the architecture boilerplate, but now I see I would still have to implement it and therefore I can use the knowledge of the architecture to download the correct binary right away, skipping the download script. So this issue is actually not a necessity – feel free to close it if you want to.