BREAKING CHANGE: Cut new release (#187)

thegraphnetwork · Oct 10, 2022 · aae229a · aae229a
1 parent 01f5f85
commit aae229a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -16,15 +16,15 @@
 - [ ] I've used pre-commit hook locally.
 - [ ] I've written tests for all new methods and classes that I created.
 - [ ] I've written the docstring in Google format for all the methods and classes that I used.
-- [ ] Semantic-release prefix title used:
+- [ ] Semantic-release prefix title used (case sensitive):
   - Use the prefix `chore(docs):` for Examples / docs / tutorials / dependencies update
   - Use the prefix `fix:` for a bug fix
     (non-breaking change which fixes an issue).
   - Use the prefix `chore(improvement):` for an improvement
     (non-breaking change which improves an existing feature).
   - Use the prefix `feat:` for a new feature
     (non-breaking change which adds functionality).
-  - Use the prefix `breaking change:` for a breaking change
+  - Use the prefix `BREAKING CHANGE:` for a breaking change
     (fix or feature that would cause existing functionality to change).
   - Use the prefix `chore(security):` for a security fix.
 

diff --git a/scripts/ci/pr-title-linter.sh b/scripts/ci/pr-title-linter.sh
@@ -2,4 +2,4 @@
 
 set -e
 
-echo "${1}" | grep -Ei "^(chore|fix|docs|feat|breaking change|test)(\(.+\))?\:"
+echo "${1}" | grep -E "^(BREAKING CHANGE|chore|fix|docs|feat|test)(\(.+\))?\:"
Original file line number	Diff line number	Diff line change
Expand Up		@@ -2,4 +2,4 @@

		set -e

		echo "${1}" \| grep -Ei "^(chore\|fix\|docs\|feat\|breaking change\|test)(\(.+\))?\:"
		echo "${1}" \| grep -E "^(BREAKING CHANGE\|chore\|fix\|docs\|feat\|test)(\(.+\))?\:"