Container build workflow not triggered by release

[bedroge]

The workflow does have:

  release:
    types: [published]

But this doesn't seem to work. Probably caused by:

When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.

We need to find some other way to automatically build new containers after the release (and, hence, the new client packages) has been published.

[bedroge]

Maybe it should be triggered by (all) pushes to main (or when a tag is created?) AND after successful completion of the client package workflow. See: https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#workflow_run

[bedroge]

Alternatively, we can use a PAT:
https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token