Does square/cashapp libraries follow any sort of c...

# squarelibraries

[Colton Idle]

Does square/cashapp libraries follow any sort of changelog/readme conventions for how to ship with a release?

I'm following a more CI/CD workflow at a new company I'm at, and we want an automated way to generate the release notes after a build is created. We sorta decided on having a bunch of empty lines in an UNRELEASED.md and when the CI goes off, it takes everything there and puts it in release notes (like how gitlab does it: https://about.gitlab.com/blog/2018/07/03/solving-gitlabs-changelog-conflict-crisis/)

I can't help to think that library developers (since releases are typically infrequent) have some sort of system in place as well where documentation/markdown is updated with a PR rather than just keeping track of changes in their notes and then writing out those notes fully just in time when a release is created.

[evanchooly]

i have a plugin that generates the release notes based on the closed GH issues but the notes are drafts until I release. the issues are separated out by type/tag. then when I release, i update the generated notes with any specific details (usually none) then publish the changes.

[evanchooly]

could probably just be a GH action now that i'm on there but I don't know that it's worth the effort

[Javier]

Gradle changelog plugin by jetbrains