From fb23e417542dbbfd37b56875a60ed124ed5109c6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jakob=20M=C3=B6ller?= <jakob.moeller@sap.com>
Date: Tue, 19 Nov 2024 11:17:09 +0100
Subject: [PATCH] chore: add breaking change release label (#1102)

<!-- markdownlint-disable MD041 -->
#### What this PR does / why we need it

makes sure that we can use the `breaking-change` label to correctly mark
changes that can lead to regressions if not taken care of.

#### Which issue(s) this PR fixes
<!--
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
---
 .github/release-drafter.yml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.github/release-drafter.yml b/.github/release-drafter.yml
index 61c15d5e1e..6827c023ff 100644
--- a/.github/release-drafter.yml
+++ b/.github/release-drafter.yml
@@ -13,6 +13,9 @@ exclude-labels:
   - 'triage/wont-fix'
   - 'triage/invalid'
 categories:
+  - title: '‼️ Breaking Changes'
+    labels:
+      - 'breaking-change'
   - title: '🚀 Features'
     labels:
       - 'kind/enhancement'