From 6564b12d6ad643bce16018ce6912ffed7f7890b2 Mon Sep 17 00:00:00 2001
From: Rico Huijbers <rix0rrr@gmail.com>
Date: Thu, 20 Aug 2020 18:32:23 +0200
Subject: [PATCH] chore: clarify that breaking changes are for experimental
 APIs

Change the "BREAKING CHANGES" header in the CHANGELOG to
"BREAKING CHANGES TO EXPERIMENTAL FEATURES" to make it sure that
stable features are not being broken.
---
 bump.sh | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/bump.sh b/bump.sh
index 4e27012be15c7..028779e5a748d 100755
--- a/bump.sh
+++ b/bump.sh
@@ -21,3 +21,13 @@ echo "Starting ${version} version bump"
 
 # Generate CHANGELOG and create a commit (see .versionrc.json)
 npx standard-version --release-as ${version}
+
+# I am sorry.
+#
+# I've gone diving through the code of `conventional-changelog` to see if there
+# was a way to configure the string and ultimately I decided that a 'sed' was the simpler
+# way to go.
+sed -i.tmp -e 's/BREAKING CHANGES$/BREAKING CHANGES TO EXPERIMENTAL FEATURES/' CHANGELOG.md
+rm CHANGELOG.md.tmp
+git add CHANGELOG.md
+git commit --amend --no-edit