[RFE] ci-automation: Publish SDK container to ghcr for releases #739
Description
Current situation
When releases are done we have to build and publish the SDK container to ghcr manually at the moment.
Since we do the release in the original pipeline and no the new one, this kind of makes sense.
However, as soon as we use the new pipeline for releases, it should also publish the SDK container to ghcr automatically.
Impact
Lack of automation if we move to the new pipeline
Ideal future situation
When we move to the new pipeline for releases, we don't have to publish the SDK container to ghcr manually.
Maybe we could even run the new pipeline for a release to have it publish the SDK container even if we don't make use of the other artifacts yet.