fix: build dir that dont exist yet

[caarlos0]

if the build.dir doesn't exist, ignore it while checking the go version.

IMHO, its unlikely that the before hook of a build will create a folder and set a go wrapper in there...

For now I think we can just ignore the dir if we fail to stat it.

cc/ @jorng

closes #2434

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/goreleaser/goreleaser/CDd9VcyT6LhH4fxgJJ2Jm3XrVe3b
✅ Preview: https://goreleaser-git-build-goreleaser.vercel.app

[codecov]

Codecov Report

Merging #2435 (f15671f) into master (70057e8) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #2435      +/-   ##
==========================================
+ Coverage   83.01%   83.02%   +0.01%     
==========================================
  Files          84       84              
  Lines        6165     6169       +4     
==========================================
+ Hits         5118     5122       +4     
  Misses        894      894              
  Partials      153      153              

Impacted Files	Coverage Δ
internal/builders/golang/targets.go	97.19% <100.00%> (+0.10%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 70057e8...f15671f. Read the comment docs.

[jorng]

Makes sense. Setting Dir during the version check more specifically for the instance that both Dir and GoBinary are set, in case GoBinary is a relative path.

That's how I hit the bug originally. I wrote a wrapper script to "natively" compile for darwin/amd64 when running on darwin/arm64 using Rosetta. The builds all failed when I had Dir+GoBinary set.