When new members are added to a class we may forget to increase the versionNumber of the TObject class inside the header at the ClassDef definition.
ClassDef( ClassName, versionNumber)
We need a test in the pipeline that writes a root file with the previous definition of the modified classes and tries to read it with the new version. If no warning occurs we do nothing, but if we get a warning the pipeline should increase automatically the value of versionNumber.
I though the root file could be created with the previous version in the pipeline.
Perhaps we could have a macro.C that is called in the pipeline and creates a temporary ROOT file, with all TRestMetadata classes found in the repository, and try to read them with the next version?