I tried that and indeed it can be compiled again.
But it also makes me very nervous. Does that mean that the KeyboardioHID is a moving target? It may happen (as it did now) that without any changes on my side my firmware will not compile since it is based on a library that is not “pinned” to a specific version?
I have used “Chrystalis-Firmware-Bundle” as the base for my custom firmware image (as suggested by algernon) since I want deviate as less as possible from the official default image.
Now it seems this will actually make my whole custom firmare extremely unstable! If I want to get back in time and compile an image I created a month ago, this will fail as I will not be able to provide the necessary depenencies in the correct version.
That sounds to me that the KeyboardioHID is a submodule in a different project. Why not for the Chrysalis-Firmware-Bundle?