ci: check goreleaser options are still compatible

[wasaga]

Summary

goreleaser deprecated a lot of options and in general we don't want to be caught by a surprise during release process.

we will run a check once a month to see if we're compatible with latest goreleaser. if we're incompatible, we would have this action failing with details like

  • loading config file                              file=.github/goreleaser.yaml
  ⨯ command failed                                   error=yaml: unmarshal errors:
  line 269: field empty_folders not found in type config.NFPM
  line 292: field replacements not found in type config.NFPMOverridables

Related issues

User Explanation

Checklist

• reference any related issues
• updated docs
• updated unit tests
• updated UPGRADING.md
• add appropriate tag (improvement / bug / etc)
• ready for review

[coveralls]

coverage: 64.064%. remained the same when pulling a9fea52 on wasaga/goreleaser-check into 5a4acc5 on main.

[kenjenkins]

One question: how will we notice if this action fails?

Would it be possible for this action to file an issue if this check fails? I see there's a Create an Issue action. Could we use a conditional failure expression to file/update an issue if this check fails?

[wasaga]

i think there's an email alert when action fails, but opening an issue might be nice indeed. not sure how to prevent duplicate issues being open each time the action runs though.