Completing the TAS installation may require some trial and error. If multiple iterations are needed during bootstrapping of this feature, additional sub-versioning should be used such as v0.4.1, v0.4.2 etc, and once the TAS installation is complete and verified, the final release should be saved in the catalog as v0.4 with no additional minor/patch version.
It would be most ideal to be able to do this via script if possible.
the 0.5 release should include the following:
Completing the TAS installation may require some trial and error. If multiple iterations are needed during bootstrapping of this feature, additional sub-versioning should be used such as v0.4.1, v0.4.2 etc, and once the TAS installation is complete and verified, the final release should be saved in the catalog as v0.4 with no additional minor/patch version.
It would be most ideal to be able to do this via script if possible.