Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regressions in lakefs-spec CI #8473

Open
nicholasjng opened this issue Jan 7, 2025 · 1 comment
Open

Regressions in lakefs-spec CI #8473

nicholasjng opened this issue Jan 7, 2025 · 1 comment

Comments

@nicholasjng
Copy link
Contributor

Hey all, happy new year! We encountered a regression in our tests from updating to lakefs-sdk v1.48.0, which was released today.

You can find a failed job summary here: https://github.com/aai-institute/lakefs-spec/actions/runs/12656491949/job/35269165597

All of the now-failing tests verify that a commit requested through the lakefs wrapper was actually made, by comparing the commit message of HEAD against the one that was given in the transaction to create a commit with.

I see "squash merging" in the release notes, did something change recently in the lakefs.Branch API?

@nicholasjng
Copy link
Contributor Author

See aai-institute/lakefs-spec#313.

Any particular reason why squash-merging is the default? Maybe I misunderstand, but I think it's very easy to wreck branch history by not knowing about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant