#52301: ci: label PRs to main with the major version after merging
Description of Change
This will let us have a view on the release project boards that show all PRs that landed on a given major. After the release branch is cut our processes label backports with the major label, but PRs targeting main never get a major label. Once they've merged we know what their major version will be, so apply the label at that point.
This also updates workflows to add PRs to the correct project and set a "Semver" field accordingly so we can use it for grouping PRs by their semver type.
I've back populated the labels for 44-x-y and here's what the project view looks like: https://github.com/orgs/electron/projects/130/views/5
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
Release Notes
Notes: none
Backports
No Backports Requested
This pull request doesn't have any backports requested or created for older release branches.
What are backports?
Backports are copies of changes made to the main branch that are applied to older release branches. They ensure that bug fixes and important changes are available in maintained older versions of Electron.
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron