ci(tests): always run tests on [newver] / [rel] commits

The trivial-push threshold was skipping the test job on version-bump
commits, which are the worst time to skip — [newver] gates the build
and [rel] gates the GitHub release, so a regression there ships straight
to users.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: eyalk11

.github/workflows/tests.yml

@@ -35,6 +35,18 @@ jobs:
             echo "workflow_dispatch -> always run"
             exit 0
           fi
+          # Force tests on commits that gate the build chain: [newver]
+          # triggers build-installer, [rel] triggers a GitHub release.
+          # Skipping tests on those pushes is exactly the worst time to
+          # skip them.
+          msg='${{ github.event.head_commit.message }}'
+          case "$msg" in
+            *'[newver]'*|*'[rel]'*)
+              echo "should_run=true" >> "$GITHUB_OUTPUT"
+              echo "commit message contains [newver] or [rel] -> run tests"
+              exit 0
+              ;;
+          esac
           # First push to a branch sends BEFORE as 40 zeros; diff against the
           # empty tree in that case so every file counts as added.
           if [ -z "$BEFORE" ] || [ "$BEFORE" = "0000000000000000000000000000000000000000" ]; then

src/compare_my_stocks/current_random.py

@@ -1 +1 @@
-RANDOM="759382839"
+RANDOM="974842911"