What the developer wrote
Authored by Hennadii Stepanov
ci: Add weekly schedule
What changed, and why it matters
This commit adds a weekly timer to the project's GitHub Actions CI workflow so tests run automatically every Monday morning. It is purely an infrastructure/maintenance change and does not modify any cryptographic code, build scripts, or user-facing behavior.
No security action required. This is a routine CI scheduling change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a schedule trigger to .github/workflows/ci.yml with a cron expression 22 2 * * 1 (2:22 UTC every Monday). The stated purpose is to run CI on the default branch weekly and warm Docker caches after key rotation. No code, dependencies, secrets, permissions, or job definitions are changed.
Changed components
.github/workflows/ci.ymlInspect captured patch +4 / −0
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 3e74f3d..308035c 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -6,6 +6,10 @@ on:
- '**'
tags-ignore:
- '**'
+ schedule:
+ # Run on the default branch every Monday morning.
+ # This also warms the Docker caches after key rotation.
+ - cron: '22 2 * * 1'
concurrency:
group: ${{ github.event_name != 'pull_request' && github.run_id || github.ref }}
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.