Really insightful post ran into a similar issue recently and was also surprised that adding a new enum value triggered a compatibility error. Totally agree that this makes managing evolving schemas in Pub/Sub pretty tricky. Curious to hear how others are handling this switching to strings might be the safer route, but feels like a compromise.