[SPARK-55102] Upgrade com.gradleup.shadow to 8.3.9#469
Closed
dongjoon-hyun wants to merge 1 commit intoapache:mainfrom
Closed
[SPARK-55102] Upgrade com.gradleup.shadow to 8.3.9#469dongjoon-hyun wants to merge 1 commit intoapache:mainfrom
com.gradleup.shadow to 8.3.9#469dongjoon-hyun wants to merge 1 commit intoapache:mainfrom
Conversation
peter-toth
approved these changes
Jan 20, 2026
Member
Author
|
Thank you, @peter-toth ! |
Member
Author
|
Merged to main. |
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
2 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.
What changes were proposed in this pull request?
This PR aims to upgrade
com.gradleup.shadowto 8.3.9.Why are the changes needed?
To bring the latest bug fixed versions.
BufferedOutputStreamwhen writing the Zip file to improve performance GradleUp/shadow#1579PropertiesFileTransformerin8.3.7GradleUp/shadow#1493compilescope GradleUp/shadow#1488Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.