httpretry VS versioninfo

Requests uses the standard HTTP client so you can plug-in retries off the shelf. Resty artificially locks you into its own ecosystem.

Oh, also https://github.com/carlmjohnson/versioninfo . Always need that.

Don’t. It’s obsolete. Just use debug.ReadBuildInfo()

That’s obsolete. See https://github.com/carlmjohnson/versioninfo. Even if it weren’t, Make is an inappropriate tool. Because it is based on file modtimes, it can’t react to git hash changes. You just have rerun the steps every time, at which point Bash is a less awful language.

Go 1.18 updates the debug info to also include the git status of the build. See https://github.com/carlmjohnson/versioninfo

I use this trick in my versioninfo package. Obviously, it can't give you other tags, but most of the time the tag you want to know about is v1.2.3 anyway, and since tags are mutable but the Go sum DB is immutable, this is safer than just saying what tag was on disk at build time.

I subscribed to GH activity for the correspondence friendliness-enhancing library by the author:

https://github.com/carlmjohnson/versioninfo/

The primary motivation curiousity to learn if this becomes "the [best/default] way" folks reach for when leveraging BuildInfo to deliver explicit binary versioning.