chore(ci): Bumped pyiceberg to v0.11.1#4297
Merged
Yicong-Huang merged 1 commit intoapache:mainfrom Mar 16, 2026
Merged
Conversation
github-actions
bot
added
engine
dependencies
Contributor
|
@Ma77Ball I hope the description is accurate.
I just triggered the CI execution in the main repo, if you have confirmed the CI passing previously, please attach a link to the CI run (if it ran on your fork). |
Contributor
Author
|
@Yicong-Huang, here is the link: https://github.com/Ma77Ball/texera/actions/runs/23166483855 (I'll also include it in pr description) |
Contributor
Thanks! And yes please include such a link in the PR description. it can make review easier. |
Yicong-Huang
approved these changes
Mar 16, 2026
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 PR?
Bumps PyIceberg from v0.8.1 to v0.11.1
Any related issues, documentation, discussions?
closes: #4099
How was this PR tested?
Was this PR authored or co-authored using generative AI tooling?
No