Don't totally agree. If you use something like avro, and make sure the schema's are backwards compatible consumers can use the newer schema when they want/need.
See my answer concerning API evolution on Twitter:
@sschrass You always have to deal with API evolution, even your domain events evolve over time. By separating the event sourcing events and the public API events gives you the freedom to evolve the API in a controlled way.
07:31 AM - 29 Jun 2019
I hope nobody thinks exposing your event sourcing events 1:1 to an external API is a good idea. Still evolution to the event sourcing objects should be controlled if used by multiple teams.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.