@thaJeztah regarding your comments-

Perhaps inline this for the lines that need this instead of exporting if we only want it for golangci-lint?

The remainder of the script is just go get's so it was intentional to apply it globally.

Regarding why the -u was removed - this is actually what was causing the failure. The -u does not prevent go from grabbing the latest/master branch why may be broken in some way. I found this explanation in the golangci-lint website: https://golangci-lint.run/usage/install/#ci-installation

Note: such go get installation aren't guaranteed to work. We recommend using binary installation.

Why?
go get installation isn't recommended because of the following points:

some users use -u flag for go get, which upgrades our dependencies. Resulting configuration wasn't tested and isn't guaranteed to work.
go.mod replacement directive doesn't apply. It means a user will be using patched version of golangci-lint if we use such replacements.
it's stability depends on a user's Go version (e.g. on this compiler Go <= 1.12 bug).
we've encountered a lot of issues with Go modules hashes.
it allows installation from master branch which can't be considered stable.
it's slower than binary installation

I figured this same logic applies to go-md2man as well. If you think we should instead use golanglint-ci's recommended installation procedure (curl to bash), I'm happy to make just that modification.

Additionally, the latest version of golangci-lint (v1.27.0) appears to require Go 1.14, so this was upgraded as well. Let me know if you prefer any changes after this explanantion.

The remainder of the script is just go get's so it was intentional to apply it globally.

Oh! I see I commented before oyu made the final changes, yes, makes sense

Regarding why the -u was removed - this is actually what was causing the failure.

Ah, gotcha, thanks!