+1 (non-binding) on the patch release. The ones mentioned by Jayce seem reasonable to add too: #3005, #3077, and #3012 More recent closed PRs look like chores and doc updates.
On Tue, Feb 24, 2026 at 10:07 AM Kevin Liu <[email protected]> wrote: > Hi all, > > I'd like to propose cutting a 0.11.1 patch release to address a regression > introduced in 0.11.0. > > *The problem: * > 0.11.0 added stricter validation on the ConfigResponse from REST Catalog > servers, but the HttpMethod enum was missing several standard HTTP methods > like PUT. This causes RestCatalog initialization to crash immediately when > connecting to Apache Polaris 1.2.0+, since Polaris returns PUT endpoints in > its config/ API response. The integration is completely broken for those > users. > > It's worth noting that the standard Iceberg REST Catalog spec does not > include PUT as a valid method. However, Polaris extends the spec with > additional endpoints that use PUT, and PyIceberg was not handling those > gracefully — instead of ignoring unknown methods, it was throwing an error. > > This was reported in issue #3074 [1] and fixed in PR #3010 [2], which has > already been merged to main. > > *Why a patch release: * > This is a critical regression — users who upgrade to 0.11.0 and use Apache > Polaris hit a hard crash on startup with no workaround short of pinning to > 0.10.x. Given that Polaris is a widely used catalog implementation, I think > it's worth getting a fix out quickly rather than waiting for 0.12.0. > > If there are other bug fixes that have been merged to main since 0.11.0 > that are worth bundling in, please reply and we can include them in the > patch. > Would love to hear thoughts from the community. If there's consensus, I'm > happy to help coordinate the release. > > Best, > Kevin Liu > > > [1] https://github.com/apache/iceberg-python/issues/3074 > [2] https://github.com/apache/iceberg-python/pull/3010 > >
