You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make a minor or RC release by creating appropriate release note PR, which leads to release branch creation upon merging.
What did you expect to happen:
A container image is built for the tag v1.10.0 but also release-1.10 which is used in testing.
Anything else you would like to add:
Note that container image build job and release image job do same thing, but only the latter matters in case of release cutting/branch creation due "workflow cannot implicitly initiate another workflow" rule.
Possible solution:
Image building in release process is bit different than the push triggered, so it likely is that we need add branch name in release workflow's list of tags to push.