📔 Objective

We would like to be able to build automations based on the fact that a Renovate PR is for a major update. This will allow us to build in more time in our planning process for the additional development and QA time necessary to evaluate and test potential breaking changes.

We currently do not have a way to know that a PR is for a major version update.

This appears to be a common need, as it's even the example in the matchUpdateTypes configuration.

I also converted the vulnerabilityAlerts to use addLabels instead of labels because it is additive (see docs), so if we had a major update that was also a vulnerability (unlikely, but still), it would keep both labels and not overwrite.

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes