add semantic release
add global verify step (optional)
test it thoroughly
there is minor problem currently with
- we put all non-secret env vars in a kubernetes config
- fromComponents can mount another components' config
- this might fail the first time a new app is deployed, e.g. on a merge request. Because if A uses config from B, A will fail unless B is already pushed to kubernetes (and the config is there).
- a possible solution might be to create envs in another step. Or to wait until the envs are created (i think that is doable with some magic)