Fixing this issue is a breaking change: <https://g...
# dev
o
Fixing this issue is a breaking change: https://github.com/treeverse/lakeFS/issues/1730 - I suggest doing it anyway, and sooner rather than later. If anyone feels otherwise, would be happy to discuss.
a
YES to fixing this, and even more yes to fixing it sooner rather than later. However I am wary of breaking existing repos. Can we mark new commits somehow? Even better, can we do something to new commits so that old commits will stand out? Then we can special-case it, and while the special case will never die -- its fragility will become less important over time.
o
I don’t know how to do this without explicitly adding a version field to commits, which i’m a little reluctant to do.. would be happy to hear suggestions
👀 1
perhaps better to discuss this in the issue itself
✔️ 1