Categorise breaking-change labels in release notes

[dacook]

What? Why?

https://openfoodnetwork.slack.com/archives/C01T75H6G0Z/p1741668548086439

• Create two new labels for PRs, to signal when it contains a “breaking change” which requires a major or minor version increment (the X or Y in vX.Y.Z).
  • The release template will be updated to categorise these
• In the future, consider creating a PR for the weekly Transifex update.
  • This means we can draft the release based on the PR’s last commit (and view the labels, before assigning the version number.

When a release is drafted, it should be easy to see if it contains any breaking changes, so we can set the version number accordingly.

What should we test?

We could test this after merging, by assigning the labels to a recently merged PR and draft a release.
Don't forget to remove the labels after testing!

Documentation updates

https://github.com/openfoodfoundation/openfoodnetwork/wiki/Releasing

• mention this when choosing a version number

[mkllnk]

Nice. Just wondering about the label naming.

[mkllnk]

Great. I'll merge and we can test this with the new release.

[dacook]

Note that the release notes generator will choose only one category for a PR. If it has two labels, it gets put in the first category.
This means that a "significant changes" PR won't also appear in another category. I guess we can choose to manually copy it in there as needed.

[mkllnk]

Note that the release notes generator will choose only one category for a PR.

Interesting. I didn't know that. So if we put Uncategorised at the bottom then we wouldn't need the exclude list for all the labels. I like it at the top though. We can keep it as is. 😄