Update Changelog

[coolblknerd]

What happened

Change long hasn't been updated since v0.7.0 has been released

Expected behavior

Changelog should be updated with every subsequent release to be aware of updates and changes.

Steps to reproduce

N/A

Versions

• Go: 1.17
• slack-go/slack: 0.9.5

[kanata2]

Thanks!
I'll consider about the operation of Changelog.
For the time being, please refer to the Release Note.

[karl-johan-grahn]

Common practice is to update CHANGELOG with each pull request. You can enforce it with for example https://github.com/marketplace/actions/changelog-enforcer. Making a release should ideally be done as part of merge to default branch too. The philosophy is that unit tests should cover all cases necessary, and that once you merge to master you automatically get a new release based on the updated change log.

[kanata2]

Thanks for advice, @karl-johan-grahn!

BTW, how about consolidating them into a GitHub release?
This is because that these days I always look at the GitHub release page first recently.

[karl-johan-grahn]

Sure, privately I do GitHub releases for my own projects, it works very well. Here's an example that does a docker publish to GHCR for every semantic tag created: https://github.com/karl-johan-grahn/devopsbot/blob/main/.github/workflows/docker-publish.yaml