Skip to content

Commit

Permalink
chore: clarify that breaking changes are for experimental APIs (aws#9876
Browse files Browse the repository at this point in the history
)

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.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
  • Loading branch information
rix0rrr authored Aug 20, 2020
1 parent 271d71c commit 7ec598e
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions bump.sh
Original file line number Diff line number Diff line change
Expand Up @@ -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

0 comments on commit 7ec598e

Please sign in to comment.