feat: add Conventional Changelog provider - #44
Conversation
Signed-off-by: Jonah Snider <jonah@jonahsnider.com>
🦋 Changeset detectedLatest commit: edacf11 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Thanks for the contribution. I did not review the code yet but I have some high-level questions about Conventional Changelog:
|
Correct, no formal output spec, just whatever the official providers emit as a reference
Both of the official presets use the same heading format, so in this case we don't need any kind of special parsing logic for them |
|
Ah yeah, the headings are different depending on output format but since we define |
✅ Deploy Preview for starlight-changelogs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
HiDeoo
left a comment
There was a problem hiding this comment.
Ah yeah, the headings are different depending on output format but since we define
versionHeadingLevel: [1, 2, 3]it handles both variants
I see, thanks for the clarification and taking the time to go with me through the details.
This looks great to me. I pushed a small refactor unifying versionHeadingLevel and isVersionHeading to a single function as it felt a bit more natural to me to only have one place to define the logic for identifying version headings.
Thanks for the contribution 🙌


Adds a Conventional Changelog provider, which is used by a bunch of tools (ex. Release Please)