[BRE-30] PR version labels

[michalchecinski]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/BRE-30

📔 Objective

Compute next version number based on label on PR: version:major, version:minor, version:patch, version:skip

If a version label is not provided on the PR, the PR is blocked from being merged.

📸 Screenshots

⏰ 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

[github-actions]

Checkmarx One – Scan Summary & Details – ab4afc70-f595-49fa-bb0d-6d931500391e

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Unpinned Actions Full Length Commit SHA	/labels.yml: [13](https://github.com/bitwarden/template/blob/BRE-30-PR-version-labels//.github/workflows/labels.yml# L13)	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

[vgrassia]

Just leaving a note here to what we discussed in Slack. This should be moved to the gh-actions repository as reusable workflows.