Thanks Danny for raising this! It's due to my manual operation to publish pyiceberg_core in the wrong branch, sorry for that!
On Mon, Jul 27, 2026 at 11:10 PM Matt Butrovich <[email protected]> wrote: > Thanks for coordinating this and for starting the discussion on how to > avoid this in the future, Danny! > > On Mon, Jul 27, 2026 at 10:52 AM Kevin Liu <[email protected]> wrote: > >> Thanks for bringing this up, Danny. I yanked the 0.10.0 release of >> pyiceberg-core on pypi. It was released off of the main branch and contains >> code that was not part of the 0.10.0 release. >> >> I think we can kick off the 0.10.1 release (using the same commit hash as >> 0.10.0) and start a vote thread. >> >> On Mon, Jul 27, 2026 at 2:54 AM Jones, Danny <[email protected]> >> wrote: >> >>> Hey folks, >>> >>> >>> >>> The release artifacts for pyiceberg-core were wrong (main branch instead >>> of 0.10.0) and have been yanked – thanks to Vova Kot for highlighting this >>> issue. >>> >>> >>> >>> We plan to run a release 0.10.1 with zero changes, simply a new set of >>> releases targeting the right branch. We’d like to have this out soon if >>> possible. >>> >>> >>> >>> Please do feel free to chime in, I’ve opened a tracking issue here too: >>> https://github.com/apache/iceberg-rust/issues/2907 >>> >>> >>> >>> Danny >>> >>
