fix: do not override GORELEASER_CURRENT_TAG

[caarlos0]

we shouldn't really do this.. as when using monorepo.tag_prefix it'll set the wrong tag to goreleaser.

that said, I'm not really sure about the auto-snapshot thingy too... seems easy enough to check on the workflow if the current commit is a tag or not, and act accordingly, no?

[codecov]

Codecov Report

Merging #370 (224618f) into master (b508e2e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #370   +/-   ##
=======================================
  Coverage   66.14%   66.14%           
=======================================
  Files           4        4           
  Lines         127      127           
  Branches       23       23           
=======================================
  Hits           84       84           
  Misses         25       25           
  Partials       18       18           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[crazy-max]

that said, I'm not really sure about the auto-snapshot thingy too... seems easy enough to check on the workflow if the current commit is a tag or not, and act accordingly, no?

Yes this was added to ease the integration in the workflow otherwise release command would fail on smth else than release tag. I guess we could make it optional.

[caarlos0]

at this point, I think we could actually make the action simpler and just download and run goreleaser without doing anything else.

we don't even need javascript for that, see https://github.com/sigstore/cosign-installer/blob/main/action.yml for example

[caarlos0]

cc/ @cpanato since you maintain the cosign action... anything you would like to share about your approach? does it work well? anything you wish to have done differently? do you automate the action release et al?

thankss <3

[cpanato]

my personal option is either you just have an action to install the tool and make sure you are installing correctly (checking signatures/shasums...) or you are very opinionated in how to expose the options to run the tool, otherwise, you will have to maintain a lot of corner cases and some are just for a really smaller audience.

[caarlos0]

@crazy-max FWIW gonna release this

[crazy-max]

@caarlos0 Major bump was the right move, thanks!