Make a new release for the API changes

[Legion2]

Can you make a new maven release and a git tag. So we can use the new API in our project and fix AmyAssist/Amy#544.

[Vogel612]

For the record: you should be able to install a local release of the new 2.1.0-SNAPSHOT version and perform the updates to your codebase without requiring an "upstream release". While this may complicate the setup for development for you, it avoids pushing a possibly unpolished release from this repository.

The breakage you refer to seems to be an artifact of how you depend onto the container-client.

[miwurster]

Until the new client impl is fully tested and validated, you could basically use the following instructions to source the current state with Maven:
https://jitpack.io/#OpenTOSCA/container-client/master-SNAPSHOT

[Legion2]

solved the problem by using the commit hash as version