@willemx I don't understand all the details, but here is how I have understood the situation:
MySensors needed to override some internal esp8266 functions to seamlessly (for the sketch developer) provide the same features that MySensors offers for other microcontrollers.
The esp team changed those functions in the 2.4.2 release, which caused compile errors for sketch developers if they upgraded the board definitions.
MySensors development version was modified to handle the new functions. By doing this, it was no longer possible to compile MySensors with the old (and still widely used, most people don't upgrade their board definitions) esp8266board definitions.
So when a new release of MySensors is done, everyone who hasn't upgraded their board definition but have upgraded the MySensors library will be unable to compile their code. On the upside, everyone who has upgraded their board definitions will be able to compile without trouble.
The only "safe" way (for future upgrades) is to remove important functionality, eliminating the need to override internal esp functions. But that will also get a lot of people into trouble.
So what we've got is that whatever we do, people will get into trouble.
There are no warnings in the esp8266 release notes because the esp team is not responsible for keeping compatibility with internal functions.
There are no warnings in the MySensors release notes because the latest MySensors release was made before the esp8266 changes were present.
There will be a note in the release notes for the next MySensors release.