We already have versioning for a regular container / for end user. This issue is more about developers who develop tags, triggers, and variables.

At some point we will be needing versioning for the templates as it will be no longer possible to keep BC for example etc.

It won't be implemented just yet as it is not needed and should be fairly "easy" to be added later. Eg each template can define a version which is by default 1. When a template defines a new version, eg 2, then we load templateName.v2.web.js instead of templateName.v1.web.js or templateName.web.js.

We save the current version of the template in the container_tag, container_trigger, ... table and will load the template based on the last saved version.