goreleaser check: run on every ci run?

[caarlos0]

a couple of ideas I had to make it more noticeable to users when they're using deprecated configs:

1. warn at the end of goreleaser release
2. instruct to have another step that runs on every commit doing goreleaser check, maybe make exit code != 0 when deprecated settings are being used

any thoughts?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[joemiller]

I like 2 because I could see incorporating it into a project's CI (eg: make lint or make test) if I wanted to block and alert someone to make changes.

[matthiasng]

I agree with @joemiller.
For local testing, the output at the end of goreleaser release is fine, but inside a pipeline, a warning gets easily lost.

@caarlos0
How about goreleaser release --no-deprecated instead of an additional command ? I think this will simplify the implementation a lot. The disadvantage is that you cannot add it to you quality checks pipeline steps.

[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.