Repository navigation
[branch-56] chore: update quinn-proto and quinn-udp to fix cargo audit (backport #27407) - #27542
Merged
xudong963 merged 1 commit intoNov 18, 2026
Conversation
) ## Which issue does this PR close? - Closes apache#27431. - Related to apache#27388, where the security audit is failing. ## Rationale for this change `cargo audit` fails against the current `Cargo.lock` on `main` with 3 vulnerabilities from advisories published after the last audit run: - `quinn-proto` 0.11.18: [RUSTSEC-2026-0523](https://rustsec.org/advisories/RUSTSEC-2026-0523), [RUSTSEC-2026-0524](https://rustsec.org/advisories/RUSTSEC-2026-0524) - `quinn-udp` 0.5.14: [RUSTSEC-2026-0538](https://rustsec.org/advisories/RUSTSEC-2026-0538) The same advisories are failing the `security_audit` check on `branch-54` and `branch-55`. ## What changes are included in this PR? `Cargo.lock` only, from ```shell cargo update -p quinn-udp -p quinn-proto ``` | Crate | Before | After | | ------------- | ------- | ------- | | `quinn-proto` | 0.11.18 | 0.11.19 | | `quinn-udp` | 0.5.14 | 0.5.16 | Both updates are semver compatible, so no `Cargo.toml` changes are needed, and no new advisories are ignored. ## What is the testing strategy for this PR? Covered by the `security_audit` CI job. Locally, `cargo audit` now passes with only allowed warnings remaining. ## Are there any user-facing changes? No, dependency version bumps in `Cargo.lock` only. Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> (cherry picked from commit 73e0b03)
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## branch-56 #27542 +/- ##
=============================================
- Coverage 83.29% 83.29% -0.01%
=============================================
Files 1170 1170
Lines 475858 475858
Branches 475858 475858
=============================================
- Hits 396367 396359 -8
- Misses 55474 55480 +6
- Partials 24017 24019 +2 see 5 files with indirect coverage changes 🚀 New features to boost your workflow:
|
zhuqi-lucas
approved these changes
Nov 18, 2026
xudong963
added a commit
that referenced
this pull request
Nov 18, 2026
## Which issue does this PR close? - Part of #24461 ## Rationale for this change #27541 and #27542 were backported to `branch-56` for RC2 after the changelog was regenerated in #27382, so they are missing from `dev/changelog/56.0.0.md`. ## What changes are included in this PR? Regenerates the changelog with `dev/release/generate-changelog.py 55.0.0 69d40d1 56.0.0`, where 69d40d1 is the current `branch-56` head, then formats it with `prettier`. This adds entries for: - #27541 (listed under breaking changes because of its `api change` label: the `FFI_ExecutionPlan` and `FFI_PhysicalExpr` layouts change) - #27542 - #27382 It also updates the commit count (1206 → 1209) and the credits. The author shown for #25337 changes from `dd-annarose` to `anna-lscr`. The script reads the current GitHub login for the commit author, so this reflects a renamed account. ## What is the testing strategy for this PR? N/A (changelog only). `ci/scripts/doc_prettier_check.sh` passes. ## Are there any user-facing changes? No 🤖 Generated with [Claude Code](https://claude.com/claude-code)
4 of 5 tasks
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.
Which issue does this PR close?
Backports #27407 to
branch-56for the 56.0.0 release tracked in #24461. The same fix was already backported tobranch-55(#27408) andbranch-54(#27409).Related to #27431 and #27388.
Rationale for this change
cargo auditfails onbranch-56with 3 vulnerabilities in the lockedquinn-protoandquinn-udpversions:quinn-proto0.11.18: RUSTSEC-2026-0523, RUSTSEC-2026-0524quinn-udp0.5.14: RUSTSEC-2026-0538These versions are in the 56.0.0 RC1 lockfile. They also fail the
security_auditcheck on #27541. RC2 is being cut anyway, so this backport keeps the vulnerable versions out of the released lockfile.What changes are included in this PR?
Clean cherry-pick of 73e0b03. Only
Cargo.lockchanges:quinn-protoquinn-udpWhat is the testing strategy for this PR?
Covered by the
security_auditCI job. Locally,cargo audit(0.22.2) reports the 3 vulnerabilities above on the currentbranch-56lockfile. After this change it exits with 0 vulnerabilities, leaving only the allowed warnings.Are there any user-facing changes?
No. These are semver-compatible dependency updates in
Cargo.lockonly.🤖 Generated with Claude Code