At present when a catalog is persisted that persistence does not seem to include a version number. It would be really nice to have that stored in such a way that the version could be determined before reading in the data (thus giving the reading code a chance to adapt to the version of the catalog being read).
In some cases we have code that saves version information as a FITS header key, but that technique doesn't always work. This came up in the context of saving VisitInfo and offering backwards compatibility for ExposureInfo tables, and again recently in
DM-8147, reading old PSF models.