Oz Katz

Thank you @geonux! Can you please confirm this issue could be closed? Or are there any changes still required on the lakeFS side?

@nopcoder @itaiad200 when do we plan on introducing this breaking change?

Thanks, that's an interesting approach! I've been thinking about this and I feel that perhaps the read path actually *is* more complex than the write path. The 3 main things...

Return of the (terribly named) [partial commit](https://github.com/treeverse/lakeFS/pull/124/)! Not to be confused, of course, with [partial commit](https://github.com/treeverse/lakeFS/issues/2512).

I believe there's also a 6th solution which might be easier to implement: [Pydantic 2.x actually ships with Pydantic 1.x](https://github.com/pydantic/pydantic/pull/5780)! Pretty much for all the same reasons this issue exists....

@N-o-Z we can either override the templates or add a post processing step, no?

@N-o-Z @itaiad200 @arielshaqed so 2-3 possible "cheap" solution: 1. [unpin pydantic](https://github.com/huggingface/datasets/issues/5398) a-la HuggingFace (assuming generated SDK doesn't use any of the features that break between 1 and 2) 2. Use...

@arielshaqed This is a great idea and I think deserves a proposal on its own right! Just clarifying: this doesn't _solve_ the issue (or at least not all occurrences of...