Adding 'go' as the release type makes changes to 'CHANGES.md' instead of CHANGELOG.md

[atreya2011]

#890

I noticed a recent pull request adds a generic go release type and the documentation is not up to date to reflect the same.

[atreya2011]

It also seems like the go release-type creates CHANGES.md instead of updating an existing CHANGELOG.md.

Is there any way to override this behaviour?

It seems like setting the changelog-path in the release-please-action does not seem to override this behaviour...

I am NOT able to override this behavior even after setting up the release-please bot with the following release-please.yml

releaseType: go
handleGHRelease: true
changelogPath: CHANGELOG.md

[bcoe]

@codyoss is it common for go to use CHANGES.md rather than CHANGELOG.md? or was this design decision specific to how we were doing things on our team?

[codyoss]

@bcoe CHANGES was a pre-existing pattern that our teams Go libraries had used. I think in general CHANGELOG is more prevalent, but even then I don't actually see most projects use them as they seem to just favor using Github releases.

[bcoe]

@codyoss I think we use go-yoshi everywhere for our internal stuff now? wondering if we could make the go releaser use CHANGELOG, and address @atreya2011's hiccup.

[codyoss]

@codyoss Yup, we are fully migrated. That sounds good to me!

[abemedia]

Any update on this? Would be great if the changelogPath option actually worked but even just changing the go releaser to CHANGELOG.md would already be good!