Skip to content

Update cryptography package to close security alerts#823

Merged
seapagan merged 2 commits intomainfrom
security/update-cryptography
Feb 12, 2026
Merged

Update cryptography package to close security alerts#823
seapagan merged 2 commits intomainfrom
security/update-cryptography

Conversation

@seapagan
Copy link
Owner

@seapagan seapagan commented Feb 12, 2026

Summary by CodeRabbit

Release Notes

  • Chores
    • Updated cryptography package to version 46.0.5 across development and production dependencies.
    • Enabled automatic lock file maintenance to keep dependencies up-to-date.

Signed-off-by: Grant Ramsay <seapagan@gmail.com>
Signed-off-by: Grant Ramsay <seapagan@gmail.com>
@seapagan seapagan self-assigned this Feb 12, 2026
@seapagan seapagan added the security Security Fixes label Feb 12, 2026
@coderabbitai
Copy link

coderabbitai bot commented Feb 12, 2026

📝 Walkthrough

Walkthrough

Configuration update to enable automatic lock file maintenance in Renovate, alongside minor dependency version upgrades. The cryptography package is updated from version 46.0.3 to 46.0.5 across both development and production dependency files.

Changes

Cohort / File(s) Summary
Configuration Update
.github/renovate.json
Added lockFileMaintenance property with enabled: true to enable automatic lock file maintenance.
Dependency Updates
requirements.txt, requirements-dev.txt
Updated cryptography package from version 46.0.3 to 46.0.5 in both files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop, a skip, dependencies shine bright,
Cryptography updates to keep systems tight,
Lock files maintained with automated care,
The rabbit grins—safety's in the air!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating the cryptography package to address security concerns, which aligns with the changes in requirements.txt and requirements-dev.txt.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch security/update-cryptography

No actionable comments were generated in the recent review. 🎉


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codacy-production
Copy link

codacy-production bot commented Feb 12, 2026

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
+0.00% (target: -1.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (23ac77e) 2445 2445 100.00%
Head commit (18831a9) 2445 (+0) 2445 (+0) 100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#823) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

@seapagan seapagan merged commit 0b3ddf2 into main Feb 12, 2026
19 checks passed
@seapagan seapagan deleted the security/update-cryptography branch February 12, 2026 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security Security Fixes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant