New releases temporarily break install script

[joey-toro]

Summary

When a new release of trufflehog is tagged in GitHub, it initially does not have binary assets associated with it, which causes the install script to fail until the "Release" CI run finishes (which can take approximately 15 minutes).

Expected Behavior

Install script should succeed, even if a new version of Trufflehog has just been tagged/published

Actual Behavior

The install script fails with HTTP 404 when trying to fetch binaries (because they have not yet been published).

Steps to Reproduce

1. After a new Trufflehog release has recently been tagged (within ~15 minutes), run the release script (curl -sSfL https://raw.githubusercontent.com/trufflesecurity/trufflehog/main/scripts/install.sh | sh -s -- -b /usr/local/bin)
2. Observe output:

   trufflesecurity/trufflehog info checking GitHub for latest tag
   trufflesecurity/trufflehog info found version: 3.95.2 for v3.95.2/linux/amd64
   trufflesecurity/trufflehog err http_download_curl received HTTP status 404
   

Additional Context

Here's what the latest release looks like at the time of writing. This release is tagged as "latest" but the only asset is the source code:

Contrast with an earlier release, which has binary assets:

References

Perhaps related to #4750, although I think that issue lasted longer than 15 minutes.

• 3.93.4 is not installing when using the install script #4750