fix: update rustls-webpki to 0.103.10 (security alert #11, partial)#146
Closed
fix: update rustls-webpki to 0.103.10 (security alert #11, partial)#146
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
No reviewable files after applying ignore patterns. |
Member
Author
|
Closing — this branch already had its fix merged via #145. No new changes needed. |
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
1 participant
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.
Security Fix — rustls-webpki
Addresses Dependabot security alert #11: webpki has a certificate revocation enforcement bug (MEDIUM severity).
What was fixed
rustls-webpki 0.103.9 → 0.103.10— updated in Cargo.lock,cargo checkpassesWhat remains (requires Domingo's attention)
rustls-webpki 0.102.8— not fixable via lock update — pinned byrustls v0.22.4(viahyper-rustls v0.25.0 → libsql v0.9.30), which requires^0.102. No patched release exists in the 0.102.x series; the fix only exists in 0.103.x. Requires upgradinglibsqlto a version pulling inrustls >= 0.23.@Domingo — the libsql upgrade needs your review/sign-off as this affects the database layer. The 0.102.8 alert will persist until that's addressed.
Closes partial: alert #11 (the 0.103.x instance)