# 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:** 4
**Page:** 1
### Author:  [@alex180500](https://discourse.julialang.org/u/alex180500)
#### Post date: [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/1 "2025-07-05T11:43:47Z")
I wanted to automate the process of commenting the latest commit to trigger the JuliaRegistrator. I also wanted this automation to include a changelog based on conventions like Conventional Commits.
For this reason I created [GitHub - alex180500/JuliaRegisterChangelog: Automatic changelog and registering of a Julia package using Conventional Commits and JuliaRegistrator](https://github.com/alex180500/JuliaRegisterChangelog).
The process consists of:
1. Detect `Project.toml`version bumps
2. Check if the version has changed since the last commit and proceed only if it has
3. Generate a changelog automatically using Conventional Commits and conventional-changelog
4. Trigger JuliaRegistrator commenting on the latest commit to register the package and correctly formats the release notes
Hope anybody can find this useful! 😁
---
### Author:  [@alex180500](https://discourse.julialang.org/u/alex180500)
#### Post date: [March 30, 2026, 10:08am UTC](https://discourse.julialang.org/t/juliaregisterchangelog-a-workflow-for-automatic-package-registration-and-changelogs-based-on-conventional-commits/130488/2 "2026-03-30T10:08:05Z")
The package was updated to replace the deprecated `conventional-changelog-cli` with `conventional-changelog`.
Check it out!
---
### Author:  [@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…
---
### Author:  [@alex180500](https://discourse.julialang.org/u/alex180500)
#### Post date: [April 14, 2026, 10:39am UTC](https://discourse.julialang.org/t/juliaregisterchangelog-a-workflow-for-automatic-package-registration-and-changelogs-based-on-conventional-commits/130488/4 "2026-04-14T10:39:57Z")
Another update, fixing the npm installation of conventional-changelog and also updating the github actions to the latest version