# JuliaRegisterChangelog, a workflow for automatic package registration and changelogs based on Conventional Commits **URL:** https://discourse.julialang.org/t/juliaregisterchangelog-a-workflow-for-automatic-package-registration-and-changelogs-based-on-conventional-commits/130488 **Category:** Package Management **Tags:** release, workflow, registry, tagbot **Created:** [July 5, 2025, 11:43am UTC](https://discourse.julialang.org/t/juliaregisterchangelog-a-workflow-for-automatic-package-registration-and-changelogs-based-on-conventional-commits/130488 "2025-07-05T11:43:47Z") **Posts on this page:** 1 **Showing post:** 3

### Author: ![gdalle](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdalle/32/27854_2.png) [@gdalle](https://discourse.julialang.org/u/gdalle) #### Post date: [March 30, 2026, 2:15pm UTC](https://discourse.julialang.org/t/juliaregisterchangelog-a-workflow-for-automatic-package-registration-and-changelogs-based-on-conventional-commits/130488/3 "2026-03-30T14:15:45Z")

Maybe there is a possible synergy with the following project? > [@\[ANN\] Easier release automation with "Release Please" CI tool](https://discourse.julialang.org/t/ann-easier-release-automation-with-release-please-ci-tool/136452/10): > > I think the most sensible thing would be to gate registration by a workflow that performs the same checks by the registry: [General/.github/workflows/automerge.yml at master · JuliaRegistries/General · GitHub](https://github.com/JuliaRegistries/General/blob/master/.github/workflows/automerge.yml) Therefore, a release-please PR would only be merged after the registration CI is happy. Which is probably what we ought to be doing anyways, rather than relying on the public registry backstop CI as the only validator. (And even when the registry does catch some issues, it still requires a… --- _[View the full topic](https://discourse.julialang.org/t/juliaregisterchangelog-a-workflow-for-automatic-package-registration-and-changelogs-based-on-conventional-commits/130488)._