I can't seem to include any folders in the archive files

[dogancelik]

Hello, after 3 years, after the bot notified me about this issue, I wanted to try Goreleaser again. Downloaded the latest version. (version 0.149.0 commit: a698393)

After trying many combinations, I simply could not, include any folders that I wanted.

• It actually included the dist/ files inside the Linux tar.gz file (recursively).
• Then it moved to the Mac archive, and the Mac archive included the Linux archive file as well.
• Then in the Windows archive, the file grew as big as 2 GB then I had to cancel the process.

I even added a random file in random/file.txt and added to files exactly like that. It didn't even include that.

Here is the test config I used.
To build the project, you need to checkout the go-mod branch here or you can download the branch.

    files:
      # main.go works
      - main.go
      # random/file.txt does NOT work
      - random/file.txt
      # **/*, includes dist folder and ignores every other folder, have to quote the string
      - '**/*'
      # ./public/* does NOT work
      - ./public/*

The command I use to build and archive the project: goreleaser release --skip-publish --rm-dist, it produces config.yml.
Here's the command output, even though the archives don't include any folders (except dist).

Maybe related to #1889?

[caarlos0]

You're building on windows right?

I think that might be the issue, we recently changed our globbing library... cc/ @djgilcrease

[caarlos0]

Can you run go test -v ./... on https://github.com/goreleaser/fileglob main and clean branches and report the results?

[dogancelik]

Here's the test log.

I tested main first, then clean second.

[caarlos0]

Yeah, seems like there is a lot of things to fix 😭

[djgilcrease]

I have windows so I can take a look at this.

[caarlos0]

awesome, thanks @djgilcrease!

We should probably run tests on windows on CI as well... 🤔

[caarlos0]

FWIW, due to a go "bug", archiving from windows will not retain the binaries permissions correctly...

that said, not sure if its even worth investigating this further

check #1947