Repository navigation
docs: use * for path expansion instead of hardcoding version - #13989
Merged
kevinjqliu merged 2 commits intoSep 15, 2025
Merged
Conversation
Contributor
Author
|
looks like this value ( Line 82 in 170189e so an alternative is also to mess with the variable and change it to minor version + 1 |
huaxingao
reviewed
Sep 3, 2025
stevenzwu
approved these changes
Sep 9, 2025
Contributor
Author
|
Thanks for the review @stevenzwu @huaxingao |
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.
quality of life improvement when verifying a release.
The docs to verify release is always 1 version behind what we're actually trying to verify. For example, right now the docs shows
apache-iceberg-1.9.2.tar.gz.ascand we're verifying 1.10.This change gets rid of the version and let path expansion takes care of the work