Gomod pipe should include config env so it works with Go Workspaces and Go.mod replace directives

[bithavoc]

What happened?

goreleaser recommends using goreleaser build instead of go build to keep a single source of truth which is useful in development environments.

When working with a Go Workspace go.work, goreleaser build needs to be combined with env GOWORK=off but is not included when doing go list -m, see below.

We have a goreleaser config with the following content:

builds:
  -
    main: ./cmd/station-agent
    binary: station-agent
    env:
      - GOWORK=off
    goos:
      - linux
    goarch:
      - amd64
      - arm
      - arm64
    flags:
      - -mod=vendor
      - -tags="linux" # sqlite3 requirement https://github.com/mattn/go-sqlite3#linux
      - -v

In the step/pipe loading go mod information, goreleaser build tries to run go list -m but it fails with the following error:

failed to get module path: exit status 1: go: open /tmp/sdk-go/go.mod: no such file or directory

That's because there are some replace directives in my go.mod file.

This is not a problem outside goreleaser if we set the env variable GOWORK=off as in GOWORK=off go list -m -mod=vendor.

I already include - GOWORK=off as part of my env but internal/pipe/gomod/gomod.go is not using to call go list -m.

How can we reproduce this?

1. Create a project with a go module
2. Use a replace directive in go.mod
3. use go workspaces (go.work)
4. Run goreleaser build

goreleaser version

goreleaser version dev
goos: linux
goarch: amd64
module version: v1.11.4, checksum: h1:bmXfkrBa6xv3WzzZM7U0QCOmpFAanIm+91tFB4DYUnI=

https://goreleaser.com

GoReleaser Check

• goreleaser check shows no errors

Search

• I did search for other open and closed issues before opening this.

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

I can send a PR to make sure we execute the external command with ctx.Config.Env

[caarlos0]

so, there is a gomod.env options you can set, but seems like its not being used... will fix that, and this is indeed a bug

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.