class versioning recommendations/best practices

I'm running into issues where new class versions are changing serialVersionUIDs and throwing deserialization exceptions when a user with an existing session holding serialized data from an old class version tries to view a page. Are there any particular recommendations or best practices on how to handle incompatible serialization versions with Spring Session? Is there any manageable way to handle this in a Web application, such as at least saying "there was a problem" and explicitly expiring the session so the user can log back in?

Start by reviewing Spring Session's handling of serialized sessions and failures during web requests. The issue names no files or tests, so first locate the session deserialization and expiration paths. Done would be clear documented guidance for incompatible class versions and the available way to report the problem and expire the session.