[SPARK-46113][BUILD][DOCS] Update pydata_sphinx_theme version requirement to >=0.13
#44027
Conversation
This file contains 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
itholic
changed the title
pydata_sphinx_theme version requirement to >=0.13pydata_sphinx_theme version requirement to >=0.13
HyukjinKwon
approved these changes
Nov 27, 2023
|
Merged to master. |
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.
What changes were proposed in this pull request?
This PR proposes to update the version requirement for
pydata_sphinx_themeinrequirements.txtfrom==0.13to>=0.13. This change allows the installation of the latest maintenance releases ofpydata_sphinx_theme, ensuring we have the most up-to-date features and fixes.Why are the changes needed?
Updating to
>=0.13ensures that we can benefit from the latest improvements and bug fixes inpydata_sphinx_themewithout being restricted to a specific patch version.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually built docs with latest versions.
Was this patch authored or co-authored using generative AI tooling?
No.