Goal

PM would like the rhdh-local repo to get updates every time we do a .0 release, so that the OOTB default points to the same current release as the helm and operator releases.

Background/Feature Origin

Thread: https://redhat-internal.slack.com/archives/C04CUSD4JSG/p1749735545824589

Why is this important?

Makes rhdh-local more easy to use OOTB
Related issue: RHIDP-1351 (arm64 builds of upstream and/or downstream builds)

Requirements

• tagRelease.sh needs to tag and generate a PR for the rhdh-local repo so that these files are updated every quarter:
  • https://github.com/redhat-developer/rhdh-local/blob/main/compose.yaml#L26
  • https://github.com/redhat-developer/rhdh-local/blob/main/compose.yaml#L52
  • https://github.com/redhat-developer/rhdh-local/blob/main/README.md#changing-the-container-image

• https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/docs/RELEASE_GUIDE.adoc should mention that rhdh-local is now also being updated no GA day when we tag the repos

Unknowns

• should we use pinned digests like we do in helm and operator? (update with every .z release); or is a floating tag :1.6 good enough for this local installation? (update only on .0 releases)
• is linking to quay.io/rhdh acceptable, or should we default to using the reg.rh.io GA releases only?
• should we remove mention of the unsupported arm64 community builds if the goal is to make rhdh-local a fully GA supported thing?
• do we want to start publishing the same r.r.io 1.y.z tags to quay.io/rhdh so that we can point to 1.7.2 instead of just 1.7 ?