Is GoReleaser Pro required for footer release?

[cafferata]

I have a pull request and test setup/GoReleaser release ready for the GoReleaser release footer. However, I started to doubt whether this feature is available without the Pro because I could not get it to work out of the box. That's why I'm checking in, can I use this feature? Or am I overlooking something else?

   # Footer for the release body.
   #
   # Templates: allowed
   footer: |
     ## Thanks

     Those were the changes on {{ .Tag }}!

   # Footer for the release body.
   #
   # This feature is only available in GoReleaser Pro.
   # Since v1.20 (pro)
   footer:
     # Loads from a URL.
     from_url:
       # Templates: allowed
       URL: https://foo.bar/footer.md
       footers:
         x-api-token: "${MYCOMPANY_TOKEN}"

     # Loads from a local file.
     # Overrides `from_url`.
     from_file:
       # Templates: allowed
       path: ./footer.md

Source: https://goreleaser.com/customization/release/?h=footer#github

[caarlos0]

Hey, for the footer as a plain string, no, it shouldn't need pro for it.

If you want ot use from_url or from_file, then yes, pro is needed.

[cafferata]

Thanks, my setup worked. However, the release notes were so large that GitHub did not show them. Would you mind if I provided a GitHub pull request that I think would clarify the difference in the code example/provide more consistency?

[caarlos0]

ah, gotcha

no problem at all, feel free to PR it

thanks 🙏

[cafferata]

For reporting. GitHub pull request #4652 is ready.

P.S. Initially I wanted to merge the two footer: configurations. However, due to the YAML multiline string this gave an invalid YAML code example.