Testing and releasing AAS sets

It would be a good idea to follow the versioning of shells more rigorously and automatically check consistency of shells.

It certainly benefits the project in the long run, assuming there will be multiple updates to template shells and to shells derived from those. What first comes to mind is to use aas-core-works and set up CI pipeline for testing.

However, compressed shells don’t integrate well in git. Going one step further, it might be even possible to extract shells into plaintext, storing binary data somewhere else. Reading and diffing uncompressed, for example, JSON files, would be much easier than loading AASX into Package Explorer or AAS-Designer.