CI: release-images building occurs on the last commit rather than on the version commit

[s373r]

Context

As part of the latest build, an unexpected situation occurred: the image with migrations (sqlx-cli-with-migrations) included migrations that are not related to the release.

Commits Timeline:

(from old to new)

• Feature: Private Datasets, Vol. 2 (Feature: Private Datasets, Vol. 2 #1043)
  • Massive changes, feature that is getting ready to be rolled out ca5a4d6
• v0.220.0
  • New minor version marking the release of feature changes 6930956
• 1040 prototype email gateway (1040 prototype email gateway #1048)
  • Changes related to other functionality, without release 49107c0

Analysis

• When releasing v0.220.0, (release CI workflow) extracted the repository revision that relates to the version (everything is as it should be)
• release-images & release-test-installer CI workflows work a bit differently: they wait for release to completed and only then run themselves:

  • workflow_run:
      workflows:
        - release
      types:
        - completed

• Thus, the latest code revision will be used (includes 1040 prototype email gateway changes), instead of the expected version revision

Expectations

• Ensure that release-images & release-test-installer CI workflow are executed on the expected code revision

Next steps

We have a mirror situation in kamu-data/kamu-node#178, hence the solution found should be applied in kamu-node repository as well