Repository navigation
[branch-55] chore: update version to 55.3.0 and add changelog - #27388
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.2 <[email protected]>
9 of 23 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## branch-55 #27388 +/- ##
=============================================
- Coverage 81.25% 81.25% -0.01%
=============================================
Files 1110 1110
Lines 389492 389492
Branches 389492 389492
=============================================
- Hits 316495 316483 -12
- Misses 54423 54430 +7
- Partials 18574 18579 +5 see 9 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Co-Authored-By: Claude Fable 5.2 <[email protected]>
Contributor
Author
|
Fix for failing CI: |
alamb
added a commit
that referenced
this pull request
Nov 13, 2026
## Which issue does this PR close? - Part of #26868 (55.3.0 release) ## Rationale for this change `cargo audit` is failing on `branch-55` (for example on #27388) with 15 vulnerabilities across 7 crates: - `ctutils` 0.4.2: [RUSTSEC-2026-0385](https://rustsec.org/advisories/RUSTSEC-2026-0385) - `quinn-proto` 0.11.15: [RUSTSEC-2026-0338](https://rustsec.org/advisories/RUSTSEC-2026-0338), [RUSTSEC-2026-0339](https://rustsec.org/advisories/RUSTSEC-2026-0339), [RUSTSEC-2026-0340](https://rustsec.org/advisories/RUSTSEC-2026-0340), [RUSTSEC-2026-0341](https://rustsec.org/advisories/RUSTSEC-2026-0341), [RUSTSEC-2026-0342](https://rustsec.org/advisories/RUSTSEC-2026-0342) - `rustls` 0.23.45: [RUSTSEC-2026-0346](https://rustsec.org/advisories/RUSTSEC-2026-0346), [RUSTSEC-2026-0347](https://rustsec.org/advisories/RUSTSEC-2026-0347), [RUSTSEC-2026-0348](https://rustsec.org/advisories/RUSTSEC-2026-0348), [RUSTSEC-2026-0349](https://rustsec.org/advisories/RUSTSEC-2026-0349) - `rustls-webpki` 0.103.15: [RUSTSEC-2026-0382](https://rustsec.org/advisories/RUSTSEC-2026-0382) - `zstd` 0.13.3: [RUSTSEC-2026-0391](https://rustsec.org/advisories/RUSTSEC-2026-0391) - `zstd-safe` 7.2.4: [RUSTSEC-2026-0398](https://rustsec.org/advisories/RUSTSEC-2026-0398), [RUSTSEC-2026-0403](https://rustsec.org/advisories/RUSTSEC-2026-0403) - `zstd-sys` 2.0.16: [RUSTSEC-2026-0410](https://rustsec.org/advisories/RUSTSEC-2026-0410) This follows the model of similar fixes on earlier maintenance branches: - #23607 (branch-54) - #21587 (branch-53) - #21415 (branch-52) ## What changes are included in this PR? `Cargo.lock` only, from ```shell cargo update -p ctutils -p quinn-proto -p rustls -p rustls-webpki -p zstd -p zstd-safe -p zstd-sys ``` | Crate | Before | After | | --------------- | ------ | ------- | | `ctutils` | 0.4.2 | 0.4.8 | | `quinn-proto` | 0.11.15 | 0.11.19 | | `rustls` | 0.23.45 | 0.23.46 | | `rustls-webpki` | 0.103.15 | 0.103.17 | | `zstd` | 0.13.3 | 0.13.5 | | `zstd-safe` | 7.2.4 | 7.4.1 | | `zstd-sys` | 2.0.16 | 2.1.3 | `quinn-proto` 0.11.19 adds `rand_pcg` 0.10.2 as a new transitive dependency. All updates are semver compatible, so no `Cargo.toml` changes are needed, and no new advisories are ignored. ## Are these changes tested? Yes, by CI. Locally, `cargo audit --ignore RUSTSEC-2026-0194 --ignore RUSTSEC-2026-0195` (the command CI runs on this branch) 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 <[email protected]>
Co-Authored-By: Claude Fable 5.2 <[email protected]>
This was referenced Nov 13, 2026
Merged
Contributor
Author
|
Thank you -- will cut this release later this afternoon |
mbutrovich
pushed a commit
that referenced
this pull request
Nov 14, 2026
…t (backport #27407) (#27408) ## Which issue does this PR close? - part of #26868 - Backport of #27407 to `branch-55` (only `quinn-udp` needs updating here, `quinn-proto` is already 0.11.19) - Related to #27431 and to #27388, where the security audit is failing. Co-authored-by: Claude Fable 5.2 <[email protected]>
CuteChuanChuan
pushed a commit
to CuteChuanChuan/datafusion
that referenced
this pull request
Nov 14, 2026
) ## 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 <[email protected]>
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?
55.3.0(patch) Release (Nov 2026) #26868.Rationale for this change
Prepare the 55.3.0 patch release.
What changes are included in this PR?
Bumps the version from 55.2.0 to 55.3.0 in
Cargo.toml,Cargo.lockand the docs, and addsdev/changelog/55.3.0.md.Are these changes tested?
No code changes. The changelog comes from
dev/release/generate-changelog.py 55.2.0 branch-55 55.3.0.Are there any user-facing changes?
No.