Add a version file input

[acouvreur]

Locally installed version of goreleaser does not always match the one used in the CI pipeline.

That discrepancy causes some back and forth fixing because of the changes that happen over new versions.

Support for version file across action is becoming more widespread, such as the go-version-file from actions/setup-go or the version-file input in golangci-lint-action.

Support for asdf tools-version file would be a nice feature to this action.

[caarlos0]

the go-version-file makes sense because go download itself into the right version, this is not a behavior goreleaser has, and i'm not sure if i want it to.

supporting asdf opens precedent to add support to a myriad of other tools.

i'm not sure this is something i want to support (at least for now)

[acouvreur]

the go-version-file makes sense because go download itself into the right version, this is not a behavior goreleaser has, and i'm not sure if i want it to.

supporting asdf opens precedent to add support to a myriad of other tools.

i'm not sure this is something i want to support (at least for now)

I'm not sure I understand your point, it is not about the tool being able to downlaod itself or not, it is more about providing team with a consistent way of setting the tool version in one place.

mise and asdf allow developers to set their tools as code, and I think it would be great if that action would support that input as well.

Currently, you have to update the version in two different places which is quite error prone.

I can submit a pull request if you agree with that proposal.

[caarlos0]

the point is that conceptually it's not our version file - i.e., goreleaser doesn't have anything like that.

if we could set version: 2.14.0 in .goreleaser.yml, and then goreleaser could detect that and use the right version, then yeah, this would be a no-brainer - but this doesn't exist.

and i don't think i agree with the concept of supporting version files we don't "own".

you can probably still read it in a step and then set it, even though having an option would be more convenient for you.

e.g.:

      - id: asdf
        run: |
          echo "goreleaser=$(awk '/^goreleaser / {print $2}' .tool-versions)"   >> "$GITHUB_OUTPUT"
      - uses: goreleaser/goreleaser-action@v7
        with:
          version: $steps.asdf.outputs.goreleaser

[acouvreur]

I understand your point, just want to make sure that you know that:

• actions/setup-go supports .tool-versions
• golangci/golangci-lint-action supports .tool-versions
• actions/setup-java supports .tool-versions
• actions/setup-node supports .tool-versions
• etc.

asdf and mise are becoming widely adopted across all standard actions in the ecosystem, or at least the .tool-versions file.

[caarlos0]

okay, that's a good point i didn't know about.

in that case, i'm more open to it. do you wanna PR it?

[acouvreur]

Sure, I will try to submit a PR :) Thank you

[acouvreur]

I've submitted #542 and did the testing on my repositories with evidence attached.

[caarlos0]

awesome, just reviewed!

thank you 🙏🏻