kevinjqliu opened a new pull request, #3455:
URL: https://github.com/apache/iceberg-rust/pull/3455

   ## Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax. For example `Closes #123` 
indicates that this PR will close issue #123.
   -->
   
   - Closes #. N/A. The Security audit check has failed on every PR and 
merge-queue run since four `rustls` advisories were published today: 
RUSTSEC-2026-0346, RUSTSEC-2026-0347, RUSTSEC-2026-0348 and RUSTSEC-2026-0349.
   
   ## What changes are included in this PR?
   
   <!--
   Provide a summary of the modifications in this PR. List the main changes 
such as new features, bug fixes, refactoring, or any other updates.
   -->
   
   Bumps `rustls` in `Cargo.lock` from 0.23.45 to 0.23.46, which is the patched 
version for all four advisories. This is a lockfile-only change.
   
   ## Are these changes tested?
   
   <!--
   Specify what test covers (unit test, integration test, etc.).
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->
   
   Covered by existing CI. Checked locally:
   - `cargo audit`: passed with no vulnerabilities, using the same advisory 
database as CI (1314 advisories).
   - `cargo metadata --locked`: passed.
   - `cargo check --locked -p iceberg-catalog-rest`: passed.
   
   ## AI Disclosure
   
   <!--
   
https://iceberg.apache.org/contribute/#guidelines-for-ai-assisted-contributions
   -->
   
   Prepared with GitHub Copilot. `cargo update -p rustls` also moved 
`tempfile`'s `getrandom` dependency from 0.4.3 to 0.3.4. I reverted that line 
by hand to keep the diff to `rustls` only. Reviewers may want to confirm the 
lockfile still resolves cleanly in CI.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to