To prevent issues like RHDHBUGS-2133 (test failures in the operator repo, because a release branch would deploy the next RHDH tag by default, which had breaking changes), we should pin the RHDH image to the corresponding 1.x tag, to ensure proper stability.
We can continue to deploy the `next` tag in the `main` branch.

For now, this has been done manually in the following PRs:

• https://github.com/redhat-developer/rhdh-operator/pull/1756
• https://github.com/redhat-developer/rhdh-operator/pull/1755
• https://github.com/redhat-developer/rhdh-operator/pull/1754

But we should consider handling this in the tagRelease.sh script, so that when the release-1.y branch, the files below are changed in that branch to point to :1.y instead of :next

TODO
Files to change in the release-1.x branch:

• rhdh-operator
  • https://github.com/redhat-developer/rhdh-operator/blob/release-1.8/config/profile/rhdh/default-config/deployment.yaml#L47
  • https://github.com/redhat-developer/rhdh-operator/blob/release-1.8/config/profile/rhdh/default-config/deployment.yaml#L86
  • https://github.com/redhat-developer/rhdh-operator/blob/release-1.8/config/profile/rhdh/patches/deployment-patch.yaml#L30
• rhdh-chart
  • https://github.com/redhat-developer/rhdh-chart/blob/release-1.8/charts/backstage/values.yaml#L41