CTTY commented on issue #2303:
URL: https://github.com/apache/iceberg-rust/issues/2303#issuecomment-4271917852

   @kevinjqliu  Just published the tag `v0.9.1-rc.1`! note there are some 
security audit failures so I had to cherry-pick some security fixes other than 
the blockers listed above, the current changelog for 0.9.1-rc.1:
   ```
   * Fix RUSTSEC-2026-0097 (#2331) by @blackmwk in 
https://github.com/apache/iceberg-rust/pull/2331
   * fix(s3tables): use 's3' as the default scheme (#2313) by @rchowell in 
https://github.com/apache/iceberg-rust/pull/2313
   * fix: build_fallback_field_id_map produces incorrect column indices for 
schemas with nested types (#2307) by @mbutrovich in 
https://github.com/apache/iceberg-rust/pull/2307
   * fix: incorrect Parquet INT96 timestamp values from ArrowReader (#2301) by 
@mbutrovich in https://github.com/apache/iceberg-rust/pull/2301
   * chore(deps): Bump rustls-webpki from 0.103.7 to 0.103.10 in 
bindings/python (#2278) by @blackmwk in 
https://github.com/apache/iceberg-rust/pull/2278
   * fix: explicitly set Python interpreter in maturin build to prevent using 
wrong version (#2277) by @kevinjqliu in 
https://github.com/apache/iceberg-rust/pull/2277
   * chore(deps): fix audit check and disable inherited aws sdk default 
features (#2274) by @maybe-vibe in 
https://github.com/apache/iceberg-rust/pull/2274
   * fix(python): use resolving storage for python binding (#2246) by @CTTY in 
https://github.com/apache/iceberg-rust/pull/2246
   * feat(storage): implement opendal resolving storage (#2231) by @CTTY in 
https://github.com/apache/iceberg-rust/pull/2231
   
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to