

The API specification is unaffected by this.
It only affects undocumented behavior, no documented behavior is being broken.
If you want to consider breakage of undocumented / unintended behavior as a major change, then every bug you fix would require a major version bump, since when you fix something you are essentially breaking compatibility for anyone who might have possibly relied on the existence of that unintended behavior.
I prefer
dua
overncdu
, specially when called interactively (dua i
), since you can explore the results in parallel before it finishes scanning, while it updates asynchronously.