Just a note if you wonder why I added an additional label to this PR @dangotbanned . We try to always have one of the labels listed here on each PR: https://github.com/vega/altair/blob/main/.github/release.yml. GitHub then organize each PR into its corresponding section of the release notes automatically when creating the release via GitHub's interface. I don't have a strong opinion about labels not listed there, so feel free to add more to that list if there are some additional labels/sections you think would be useful.

I looked into automating the addition of a label to each PR via a GitHub action based on the conventional commit type mentioned in the PR title, but there was no such action so I just check through the closed PRs every now and then and label the ones that are missing one of the four labels our release notes are based on.

No worries @joelostblom

I won't be able to test right now, but https://github.com/vega/altair/blob/main/.github/release.yml looks like you can map multiple labels to each title?

E.g. this had the dependencies label, which could fall under maintenance.

If that can work, I think that would be worth doing as there are other labels that wouldnt be picked up currently

Yup, we can map additional labels just like you said. Another option would be to remove the labels we haven't used much in the past like dependencies and usability. I don't really have a preference since I mostly use the four other labels, but if you believe that these additional labels are useful, then I'm happy for them to be added.