Skip to content

fix: refresh cryptography security locks - #47

Merged
AdeGneus merged 2 commits into
mainfrom
fix/cryptography-security-locks
Aug 10, 2026
Merged

fix: refresh cryptography security locks#47
AdeGneus merged 2 commits into
mainfrom
fix/cryptography-security-locks

Conversation

@AdeGneus

Copy link
Copy Markdown
Contributor

Summary

  • pin the SDK runtime constraint to cryptography 49.0.0
  • regenerate both hash-locked requirement files so CI installs the fixed release

Root cause

The dependency input accepted cryptography <50, but both CI lockfiles still pinned cryptography 48.0.1. CI therefore continued installing and auditing the stale vulnerable pin after the Dependabot constraint update.

Validation

  • 455 tests passed via uv
  • python3 scripts/check_workflows.py
  • git diff --check

@AdeGneus AdeGneus self-assigned this Aug 10, 2026
@AdeGneus

Copy link
Copy Markdown
Contributor Author

CI diagnosis: pip-audit flagged cryptography 49.0.0 as PYSEC-2026-3552; the advisory fix is 50.0.0. Updated both lockfiles and project constraints to cryptography>=50.0.0,<51 in commit 17c00df. Local validation: 455 tests passed and supply-chain guard passed.

@AdeGneus
AdeGneus marked this pull request as ready for review August 10, 2026 11:37
@AdeGneus
AdeGneus merged commit 3c35026 into main Aug 10, 2026
2 checks passed
@AdeGneus
AdeGneus deleted the fix/cryptography-security-locks branch August 10, 2026 11:37
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.

1 participant