@sasjs/adapter 4.19.0 → 4.19.1

package/.git-hooks/commit-msg

@@ -7,12 +7,33 @@ GREEN="\033[1;32m"
 commit_message=$(cat "$1")
 
 if (echo "$commit_message" | grep -Eq "^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([a-z0-9 -\*]+\))?!?: .+$") then
+   :
+else
+   echo "${RED}❌ Commit message does not meet the Conventional Commit standard!"
+   echo "An example of a valid message is:"
+   echo "  feat(login): add the 'remember me' button"
+   echo "ℹ More details at: https://www.conventionalcommits.org/en/v1.0.0/#summary"
+   exit 1
+fi
+
+# semantic-release releases only feat, fix and perf, plus any type carrying a
+# breaking `!`. Every other type merges without a release, which leaves the
+# publish job with nothing to publish - so say so, and require the author to
+# opt out in the message when that is what they intend.
+# `[skip ci]` is accepted alongside `[skip release]` because the release commit
+# semantic-release writes itself is a `chore` that carries it.
+if (echo "$commit_message" | grep -Eq "^(feat|fix|perf)(\([a-z0-9 -\*]+\))?!?: .+$") then
    echo "${GREEN} ✔ Commit message meets Conventional Commit standards"
    exit 0
 fi
 
-echo "${RED}❌ Commit message does not meet the Conventional Commit standard!"
-echo "An example of a valid message is:"
-echo "  feat(login): add the 'remember me' button"
-echo "ℹ More details at: https://www.conventionalcommits.org/en/v1.0.0/#summary"
-exit 1
+if (echo "$commit_message" | grep -Eq "\[skip (release|ci)\]") then
+   echo "${GREEN} ✔ Conventional commit, marked as not for release"
+   exit 0
+fi
+
+echo "${RED}❌ Commit type would not produce a release!"
+echo "semantic-release releases only feat, fix and perf (or a breaking ! change)."
+echo "If this commit is not meant to release, say so in the message:"
+echo "  chore(deps): refresh the lockfile [skip release]"
+exit 1

package/.pre-commit-config.yaml

@@ -0,0 +1,25 @@
+# Hooks for the pre-commit framework - https://pre-commit.com
+#
+# The repo also ships native hooks in .git-hooks/: a prettier check before the
+# commit, and the Conventional Commits and release checks on the message. The
+# `prepare` script activates them by setting core.hooksPath - but .npmrc sets
+# ignore-scripts=true, so `npm i` never runs it and a fresh clone commits
+# unchecked.
+#
+# This file is the standard route instead: install the framework once with
+# `pre-commit install`, and the secret scan and the message check run on every
+# commit. gitleaks is pinned to an exact release tag, and the message hook
+# calls the script the native hooks already use, so there is one implementation
+# of the rules.
+repos:
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.30.1
+    hooks:
+      - id: gitleaks
+  - repo: local
+    hooks:
+      - id: commit-msg
+        name: conventional commit, with a release-bearing type
+        entry: .git-hooks/commit-msg
+        language: script
+        stages: [commit-msg]