Skip to content

chore(security): update aws-lc-sys#6

Merged
hyperpolymath merged 1 commit intomainfrom
chore/security-fix-aws-lc-sys
Mar 26, 2026
Merged

chore(security): update aws-lc-sys#6
hyperpolymath merged 1 commit intomainfrom
chore/security-fix-aws-lc-sys

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Updated aws-lc-sys to fix security vulnerabilities

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c0b205f24d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -0,0 +1 @@
rust stable
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Actually bump aws-lc-sys in the dependency set

This change is presented as a security update for aws-lc-sys, but it only adds .tool-versions (rust stable) and does not update any Rust dependency manifests/lockfiles; Cargo.lock still pins aws-lc-sys to 0.37.1 just as before. That means the vulnerable dependency version remains in shipped builds, so the intended security fix is not actually applied.

Useful? React with 👍 / 👎.

@hyperpolymath hyperpolymath merged commit 16bddc8 into main Mar 26, 2026
20 of 26 checks passed
@hyperpolymath hyperpolymath deleted the chore/security-fix-aws-lc-sys branch March 26, 2026 11:59
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