The root BuildingSync element has an @version attribute allowing users to specify the version of their document. We have been writing the full version, MAJOR.MINOR.PATCH, as the choices. This is not compatible with creating patch releases though -- since the x.x.0 version was already released, it will consider any new patch version to be invalid according to that schema.
⚠️ From now on, we should only add these MAJOR.MINOR versions!
What does this PR do?
Use MAJOR.MINOR versions when specifying versions (but allow the old MAJOR.MINOR.PATCH to stick around)
Any background context you want to provide?
The root BuildingSync element has an
@versionattribute allowing users to specify the version of their document. We have been writing the full version,MAJOR.MINOR.PATCH, as the choices. This is not compatible with creating patch releases though -- since thex.x.0version was already released, it will consider any new patch version to be invalid according to that schema.⚠️ From now on, we should only add these
MAJOR.MINORversions!What does this PR do?
MAJOR.MINORversions when specifying versions (but allow the old MAJOR.MINOR.PATCH to stick around)How should this be manually tested?
What are the relevant tickets?
414
Screenshots (if appropriate)