Performance benchmarks:

See https://github.com/orgs/community/discussions/10038.

Seeing unlabeled merged PRs is as easy as this, right? Anything since december 2023 should be labeled.

That's true. Is there a way to filter to cut off further the earliest date? But if a bulk of the checklist can be automated, it would be easier to read the info from the command line.

Yes, see the docs.

@rht do you mind closing this PR? I think using the GitHub URL is automated enough for now.

As I said on #2047 (comment), once again, if almost everything in the checklist is automated, it is better off to use the CLI script. This PR is a first step in that direction. I usually don't draft the releases, but if you, @jackiekazil , and @tpike3 find the automation to be not worth it, you may close this PR.

I will do a review before the end of the week early this week (week of March 18). I want to make sure I understand things completely.

I see the vision, and I think I understand the issue. I am going to repeat it back to make sure I am not misunderstanding.
@rht - you are moving towards trying to automate the release more
@EwoutH - the script that is added seems like a simple thing that can be done in the UI, so why do it through a script?

...
@rht -- what are the other components that would be automated? I am looking for the checklist to create a parent ticket to see the whole vision. What I don't want to do is to merge this and then have it randomly hangout if that makes sense.

The steps are:

1. (automated) Use the script in this PR to check for unlabeled PRs. Do not allow to proceed until the list is empty.
2. (automated) Automatically generate a release note with https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#generate-release-notes-content-for-a-release, and auto-append this to HISTORY.md.
3. (manual) Add highlights to the release
4. (can be partly scripted) Open a PR that includes the HISTORY.md change and __init__.py version bump. Wait until it is merged.
5. (automated) Release using https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#create-a-release
6. (manual) Check on PyPI if the release is there
7. (automated) Open a PR to append -dev to the next minor release version.

As you may notice, it is much simpler than #1917 (comment), because the generate release note step (without drafting a release) already has an API.

Just to re-iterate, In my opinion, this script is unnecessary, since you can just go to https://github.com/projectmesa/mesa/pulls?q=is%3Apr+is%3Amerged+no%3Alabel+merged%3A%3E%3D2023-12-01 and see which PRs need a label yet. I also don't know yet how this helps with automation.

However, if this is useful for others I'm not against merging this.

I am going to merge based on the discuss. If we don't end up using this in the future we can remove it.