Skip to content

Update Semgrep to 1.172.0 for Python 3.10–3.14 - #120

Merged
ajinabraham merged 4 commits into
mainfrom
chore/update-semgrep-1-172
Aug 10, 2026
Merged

Update Semgrep to 1.172.0 for Python 3.10–3.14#120
ajinabraham merged 4 commits into
mainfrom
chore/update-semgrep-1-172

Conversation

@ajinabraham

Copy link
Copy Markdown
Member

Summary

  • Bump Semgrep to 1.172.0 and libsast to ≥3.1.7 (aligned with local libsast), with Python 3.10–3.14 support
  • Regenerate Pipfile.lock/requirements, refresh CI/Actions (tests, publish, CodeQL), and keep the SSLContext Semgrep fixture annotations
  • Supersedes #119 (1.168.0) with the newer Semgrep pin from libsast

Test plan

  • CI green across Python 3.10–3.14 on ubuntu/macOS
  • tox -e lint,bandit,py
  • Semgrep --validate --strict and rule tests (40/40)
  • Install with local/published libsast 3.1.7 + semgrep==1.172.0

Made with Cursor

mazen160 and others added 2 commits July 15, 2026 11:41
Bump Semgrep to 1.168.0 across packaging and CI, regenerate the locked dependency artifacts, and declare the Python 3.10 minimum required by Semgrep. Extend CI coverage to Python 3.14 and update the Semgrep fixture for newly detected insecure SSLContext declarations.
Raise the Semgrep/libsast pins to match local libsast, cover Python 3.10–3.14 in CI/tox, and refresh Actions workflows.

Co-authored-by: Cursor <cursoragent@cursor.com>
@cursor

cursor Bot commented Aug 10, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

ajinabraham and others added 2 commits August 9, 2026 19:05
Use published libsast 3.1.6 so tox can resolve deps, and add SBOM/provenance attestations with bumped Docker Actions.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@ajinabraham
ajinabraham merged commit 28764d1 into main Aug 10, 2026
12 checks passed
@ajinabraham
ajinabraham deleted the chore/update-semgrep-1-172 branch August 10, 2026 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants