Repository navigation
[branch-55] chore: update version 55.2.0 and add changelog - #26037
Merged
Merged
Conversation
6 of 21 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## branch-55 #26037 +/- ##
=============================================
- Coverage 81.21% 81.21% -0.01%
=============================================
Files 1110 1110
Lines 388606 388606
Branches 388606 388606
=============================================
- Hits 315614 315611 -3
- Misses 54444 54445 +1
- Partials 18548 18550 +2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
adriangb
approved these changes
Oct 4, 2026
Contributor
Author
|
Thanks @adriangb |
minhh-nguyen
pushed a commit
to minhh-nguyen/datafusion
that referenced
this pull request
Oct 7, 2026
…pache#26119) ## Which issue does this PR close? - Related to apache#25758. ## Rationale for this change The release README used 50.x examples and had no commands to check, download or unpack the artifacts in SVN. ## What changes are included in this PR? In `dev/release/README.md`: - Use 55.2.0 in the examples. - Step 2: add the `sed` and `cargo update --workspace` commands for the version and lockfile. - Add `svn ls` checks after the uploads, and `svn export` plus `tar xzf` commands for the release tarball. - Step 13: keep the last major release (`55.0.0` in the example) and the releases after it in the `release` SVN, with a short loop that prints the `svn delete` commands for the other releases. ## What is the testing strategy for this PR? Docs only. The `sed` commands reproduce the `Cargo.toml` and docs changes of the 55.2.0 release PR (apache#26037). The loop was run in bash, zsh and sh against a local SVN repository. ## Are there any user-facing changes? No.
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
3 participants
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.2.0(patch) Release (Oct 2026) #25758.Rationale for this change
Prepare the 55.2.0 patch release.
What changes are included in this PR?
Bumps the version to 55.2.0 in
Cargo.toml,Cargo.lockand the docs, and addsdev/changelog/55.2.0.md.What is the testing strategy for this PR?
No code changes. The changelog comes from
dev/release/generate-changelog.py.Are there any user-facing changes?
No.