[SPARK-51526] Upgrade Gradle shadow plugin to 8.3.6 #168
Conversation
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
viirya
changed the title
viirya
approved these changes
Mar 17, 2025
Signed-off-by: Jacob Salway <[email protected]>
jacobsalway
force-pushed
the
SPARK-45923
branch
from
ff1902f to
08dd4a0
Compare
Contributor
Author
|
Thanks, mislabeled with the code from the epic rather than the sub-task |
dongjoon-hyun
approved these changes
Mar 17, 2025
Member
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
+1, LGTM. Merged to main.
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.
What changes were proposed in this pull request?
Migrate the Gradle plugin given it's changed ownership and upgrade Gradle shadow plugin to 8.3.6
Why are the changes needed?
GradleUp/shadow#908
Does this PR introduce any user-facing change?
No
How was this patch tested?
Tested the build locally
Was this patch authored or co-authored using generative AI tooling?
No