Given that jj is still not 1.0 we must expect breaking changes. For example, jj 0.33.0 has changed semantics of jj undo.
If a version of lazyjj encounters a version of jj that is more recent than it was tested with, this could cause issues. Therefore I propose a warning at launch of lazyjj if the jj version is too high. The fix is usually to upgrade lazyjj.
Given that jj is still not 1.0 we must expect breaking changes. For example, jj 0.33.0 has changed semantics of jj undo.
If a version of lazyjj encounters a version of jj that is more recent than it was tested with, this could cause issues. Therefore I propose a warning at launch of lazyjj if the jj version is too high. The fix is usually to upgrade lazyjj.