Ouch:

Warning: Congrats! The gnu test tests/ls/removed-directory is now passing!
Error: GNU test failed: tests/cp/attr-existing. tests/cp/attr-existing is passing on 'main'. Maybe you have to rebase?
Error: GNU test failed: tests/ls/classify. tests/ls/classify is passing on 'main'. Maybe you have to rebase?
Error: GNU test failed: tests/ls/selinux-segfault. tests/ls/selinux-segfault is passing on 'main'. Maybe you have to rebase?
Error: GNU test failed: tests/ls/sort-width-option. tests/ls/sort-width-option is passing on 'main'. Maybe you have to rebase?
Error: GNU test failed: tests/ls/zero-option. tests/ls/zero-option is passing on 'main'. Maybe you have to rebase?
Error: GNU test failed: tests/misc/cksum. tests/misc/cksum is passing on 'main'. Maybe you have to rebase?
Error: GNU test failed: tests/misc/cksum-a. tests/misc/cksum-a is passing on 'main'. Maybe you have to rebase?
Error: GNU test failed: tests/misc/cksum-c. tests/misc/cksum-c is passing on 'main'. Maybe you have to rebase?
Error: GNU test failed: tests/misc/sm3sum. tests/misc/sm3sum is passing on 'main'. Maybe you have to rebase?

did you look at what is regressing?

I had not, but did so now:

• tests/cp/attr-existing: now tests that cp does not remove files when --attributes-only is passed (specifically, files that would be overwritten were the flag not present) cp: --remove-destination + --attributes-only should copy symlinks #2926
• tests/ls/classify: new test for new optional flag argument (--classify can now take always/auto/never) ls: --classify should be able to take optional argument #2927
• tests/ls/selinux-segfault: adds check for "segfault when printing the security context of broken symlink targets" ls: -L on broken links should return 1 #2928
• tests/ls/zero-option: new test for new flag, --zero, that uses null for line endings instead of newline ls: add support for --zero option #2929
• tests/misc/cksum, tests/misc/cksum-a, tests/misc/cksum-c, tests/misc/sm3sum: a bunch of brand new tests, someone will have to dig into what all they're testing cksum: failing GNU tests #2930

So basically, no singular issue, just various updates to the tests. Some of these seem like new functionality that will have to be added, but at least the first one seems like an actual bug being caught.

Sounds good, could you please create issues to keep track of the regressions?
thanks

I've updated my above comment with links to the respective issues.

amazing, thanks :)

let's regress then :)

I documented the change here:
uutils/coreutils-tracking@a10f9b0