ci(verify-pipeline): re-run determinism gate on lock changes

The determinism gate is path-filtered, but requirements-lock.txt (which
pins the numpy/scipy versions that *produce* the proof hash) was not in
the filter — so a dependency bump could silently drift the hash without
re-running the gate. That's how the 1.26.4 pin diverged from the
published ca58956c hash unnoticed. Add requirements-lock.txt to both the
push and pull_request path filters so this PR (and any future lock
change) actually re-runs verify.py.

Co-Authored-By: claude-flow <ruv@ruv.net>
This commit is contained in:
ruv
2026-05-31 11:39:08 -04:00
parent eb77a4732b
commit 6c3a28037b
+2
View File
@@ -7,6 +7,7 @@ on:
- 'archive/v1/src/core/**' - 'archive/v1/src/core/**'
- 'archive/v1/src/hardware/**' - 'archive/v1/src/hardware/**'
- 'archive/v1/data/proof/**' - 'archive/v1/data/proof/**'
- 'archive/v1/requirements-lock.txt'
- '.github/workflows/verify-pipeline.yml' - '.github/workflows/verify-pipeline.yml'
pull_request: pull_request:
branches: [ main, master ] branches: [ main, master ]
@@ -14,6 +15,7 @@ on:
- 'archive/v1/src/core/**' - 'archive/v1/src/core/**'
- 'archive/v1/src/hardware/**' - 'archive/v1/src/hardware/**'
- 'archive/v1/data/proof/**' - 'archive/v1/data/proof/**'
- 'archive/v1/requirements-lock.txt'
- '.github/workflows/verify-pipeline.yml' - '.github/workflows/verify-pipeline.yml'
workflow_dispatch: workflow_dispatch: