I disabled the continuous-integration/travis-ci branch protection for now so that this PR is not blocked on advancing. If @th0r you feel like this is good to go, I can add branch protections for the GitHub actions if necessary.

I wonder is it possible to add Node.js prefix to version numbers as now it's a bit not obvious what do these numbers mean?

I don't know — I can check if that's possible when I have the time ☺️

It now looks like so:

It seems quite simple to change the name to whatever we want as can be seen by fdb5a0e — feel free to make a direct code suggestion to this PR if you have a better wording in mind ☺️

I can add branch protections for the GitHub actions if necessary.

Do we need the branch protections? I'm not sure if they're necessary — a red CI should be enough for us to avoid merging pull requests.

The CLA-check of course stays as a required status check.

Do we need the branch protections?

I don't even know what is that =)

Ah, it's this one:

So one can't merge a pull request (unless they're an admin and admin overrule is allowed) if a required status check is not successful.

We could configure some or all of the GitHub Actions status checks to be required to be successful to allow merging via https://github.com/webpack-contrib/webpack-bundle-analyzer/settings/branches, from here:

Ah, ok, thanks for the explanation. I don't think we need it.

Yeah I think the same, let's keep it as it is now 👍