Repository navigation
Bump plug_crypto to 2.2.1 - #5259
Merged
Merged
Conversation
Security Review ✅
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5259 +/- ##
=====================================
Coverage 91.5% 91.5%
=====================================
Files 465 465
Lines 23787 23787
=====================================
+ Hits 21764 21766 +2
+ Misses 2023 2021 -2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR bumps plug_crypto from 2.2.0 to 2.2.1. The advisory is EEF-CVE-2026-105963, where passing a wrong-typed argument to Plug.Crypto puts the secret key base in the stack trace.
mix hex.auditstarted failing on main this morning because of it, which takes the lint job down on main and on every open branch.Nothing else moves. plug_crypto is a transitive dependency of plug and phoenix and both accept
~> 2.0, so only the one line inmix.lockchanges.Validation steps
mix deps.get && mix hex.audit. It exits clean, with only the three advisories we already ignore (cloak, cloak_ecto, cowlib).Additional notes for the reviewer
AI Usage
Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):
You can read more details in our
Responsible AI Policy
Pre-submission checklist
/reviewwith Claude Code)
(e.g.,
:owner,:admin,:editor,:viewer)