[SPARK-44956][BUILD] Upgrade Jekyll to 4.3.2 & Webrick to 1.8.1 #42669
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
panbingkun
changed the title
srowen
approved these changes
Sep 2, 2023
Member
|
Merged to master |
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?
The pr aims to upgrade
Why are the changes needed?
1.The
4.2.1version was released on Sep 27, 2021, and it has been 2 years since now.2.Jekyll 4.3.2 was released in
Jan 21, 2023, which includes the fix of a regression bug.Fix regression in Convertible module from v4.2.0 (Fix regression in Convertible module from v4.2.0 jekyll/jekyll#8786)
3.The webrick newest version include some big fixed.
https://github.com/ruby/webrick/releases/tag/v1.8.1
https://github.com/ruby/webrick/releases/tag/v1.8.0
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No.