Skip to content

ci(release): warn about breaking changes in the release notes [skip ci] - #57

Merged
TomGrobbe merged 1 commit into
legacyfrom
ci/legacy-breaking-change-notes
Aug 28, 2026
Merged

ci(release): warn about breaking changes in the release notes [skip ci]#57
TomGrobbe merged 1 commit into
legacyfrom
ci/legacy-breaking-change-notes

Conversation

@TomGrobbe

Copy link
Copy Markdown
Owner

Ports the release notes change from fivem-enhanced so both copies of build.yml stay identical, which the file's own header asks for.

The release job now scans each line's tag range for breaking commits, in both Conventional Commits forms:

  • a ! before the colon in the subject, e.g. feat(keybindings)!: ...
  • a BREAKING CHANGE: or BREAKING-CHANGE: footer at the start of a line in the body, whose text is carried into the notes as the explanation

Anything found is written above everything else in the release notes as a > [!WARNING] block, split per line (Enhanced / Legacy), separate from the changelog lists, which are unchanged. With no breaking commits the notes look exactly as they do today.

No behaviour change for this line's builds or packages.

@TomGrobbe TomGrobbe changed the title ci(release): warn about breaking changes in the release notes ci(release): warn about breaking changes in the release notes [skip ci] Aug 28, 2026
@TomGrobbe
TomGrobbe merged commit b60825d into legacy Aug 28, 2026
16 checks passed
@TomGrobbe
TomGrobbe deleted the ci/legacy-breaking-change-notes branch August 28, 2026 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants