Skip to content

fix: explictly set latest version for generated release notes#182

Merged
ndr-brt merged 1 commit intomainfrom
180-explicitly-set-latest-version
Feb 19, 2026
Merged

fix: explictly set latest version for generated release notes#182
ndr-brt merged 1 commit intomainfrom
180-explicitly-set-latest-version

Conversation

@ndr-brt
Copy link
Member

@ndr-brt ndr-brt commented Feb 19, 2026

What this PR changes/adds

Uses gh cli to generate release and explicitly pass the latest released version

Why it does that

generate the changelog correctly

Further notes

  • no need to use an action when doing it through gh cli is that easy

Who will sponsor this feature?

Please @-mention the committer that will sponsor your feature.

Linked Issue(s)

Closes #180

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

@ndr-brt ndr-brt requested a review from a team February 19, 2026 10:29
@ndr-brt ndr-brt added the bug Something isn't working label Feb 19, 2026
@ndr-brt ndr-brt merged commit 243572f into main Feb 19, 2026
6 of 9 checks passed
@ndr-brt ndr-brt deleted the 180-explicitly-set-latest-version branch February 19, 2026 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release notes are incorrect

2 participants

Comments