[main] chore: tagRelease.sh: bump to 1.10.3

[rm3l]

Manual cherry-pick of #281

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-qodo-merge]

PR Summary by Qodo

Bump pinned RHDH images to 1.10.3 (env + docs)

⚙️ Configuration changes 📝 Documentation 🕐 Less than 5 minutes

AI Description

• Bump the pinned plugin catalog index image tag from 1.10.2 to 1.10.3.
• Update the local guide example to reference the RHDH 1.10.3 container image.

Diagram

graph TD
  Dev[Developer] --> Env["default.env"] --> CatalogImg["plugin-catalog-index:1.10.3"] --> Quay[("quay.io")]
  Dev --> Doc["container-image-guide.md"] --> RhdhImg["rhdh-hub-rhel9:1.10.3"] --> Registry[("registry.redhat.io")]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Pin images by digest instead of tag

• ➕ Eliminates risk of tag mutation and improves reproducibility
• ➕ Makes rollbacks/auditing more deterministic
• ➖ Harder to read and maintain in env/docs
• ➖ Requires updating digest values for every release and mirroring process changes

2. Use a floating minor tag (e.g., 1.10)

• ➕ Less frequent maintenance for patch bumps
• ➕ Automatically picks up patch fixes
• ➖ Reintroduces the instability that prompted pinning (noted in TODO)
• ➖ Can cause unexpected changes in local behavior between runs

Recommendation: For a release cherry-pick, the current approach (explicitly bumping pinned tags to 1.10.3) is appropriate and aligns with the existing decision to avoid floating tags. Consider digests only if reproducibility issues persist or tag mutability becomes a recurring problem.

Files changed (2) +2 / -2

Documentation (1) +1 / -1

container-image-guide.mdUpdate RHDH image example to 1.10.3 +1/-1

Update RHDH image example to 1.10.3

• Adjusts the documentation snippet to reference the official RHDH container image tag 1.10.3 instead of 1.9.

docs/rhdh-local-guide/container-image-guide.md

Other (1) +1 / -1

default.envBump plugin catalog index image tag to 1.10.3 +1/-1

Bump plugin catalog index image tag to 1.10.3

• Updates the pinned CATALOG_INDEX_IMAGE tag from 1.10.2 to 1.10.3 so local runs pull the new catalog index image.

default.env

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 🔗 Cross-repo conflicts (1) 📜 Skill insights (0)

Context used

✅ Cross-repo context

  Explored: repo: redhat-developer/rhdh (sha: 84072ae9)

  Not relevant to this PR: redhat-developer/rhdh-plugins

1. Docs version mismatch 🐞 Bug ⚙ Maintainability

Description

In container-image-guide.md, the “official release” section still says “for example, 1.9” but the
updated snippet now uses the 1.10.3 image tag, which can confuse readers about what version the
example represents.

Code

docs/rhdh-local-guide/container-image-guide.md[54]

+RHDH_IMAGE=registry.redhat.io/rhdh/rhdh-hub-rhel9:1.10.3

Relevance

●●● Strong

Repo regularly updates container image guide prose/examples to keep version references consistent
and current.

PR-#161
PR-#205

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The prose immediately preceding the updated snippet still cites 1.9 as the example version, while
the snippet itself is now 1.10.3.

docs/rhdh-local-guide/container-image-guide.md[49-55]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The documentation text describes the example version as `1.9`, but the snippet was updated to `1.10.3`, creating an internal inconsistency in the same section.

### Issue Context
This is in the “Using commercially supported official images” section; the prose and the shell snippet should describe the same example version, or the prose should be made version-agnostic.

### Fix Focus Areas
- docs/rhdh-local-guide/container-image-guide.md[49-55]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Catalog index tag drift 🔗 Cross-repo conflict ≡ Correctness

Description

This PR pins rhdh-local to quay.io/rhdh/plugin-catalog-index:1.10.3, but upstream rhdh docs/CI
examples primarily document quay.io/rhdh/plugin-catalog-index:1.10 (minor tag) while showing patch
tags mainly for registry.access.redhat.com. If :1.10.3 is not published/maintained on quay.io,
rhdh-local will fail during dynamic plugin catalog download.

Code

default.env[17]

+CATALOG_INDEX_IMAGE=quay.io/rhdh/plugin-catalog-index:1.10.3

Relevance

●●● Strong

Team previously pinned away from unstable floating 1.10 resolving to 1.10.3; prefers known-good
tags.

PR-#271
PR-#205

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The PR hardcodes a quay.io patch tag for the catalog index. Upstream rhdh documentation and CI
environment variable guidance show quay.io usage with minor/CI tags and patch tags exemplified for
Red Hat registries, implying quay.io patch tags may not be part of the documented contract.

default.env[14-18]
External repo: redhat-developer/rhdh, docs/index.md [7-35]
External repo: redhat-developer/rhdh, .ci/pipelines/env_variables.sh [58-69]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`default.env` now defaults to `CATALOG_INDEX_IMAGE=quay.io/rhdh/plugin-catalog-index:1.10.3`. In the upstream `redhat-developer/rhdh` repo, docs/examples for quay.io generally use the minor tag (`:1.10`) while patch tags are exemplified on `registry.access.redhat.com`, so this default may point to a tag that is not guaranteed to exist on quay.io.

### Issue Context
If the quay.io patch tag is missing (or not kept in sync), rhdh-local’s `install-dynamic-plugins` flow will fail when it tries to pull the catalog index image.

### Fix Focus Areas
- default.env[14-18]

### Suggested fix
1. Confirm that `quay.io/rhdh/plugin-catalog-index:1.10.3` is actually published and intended to be stable.
2. If patch tags are not reliably present on quay.io, change the default back to the documented minor tag (`quay.io/rhdh/plugin-catalog-index:1.10`) and document how to use patch tags via the Red Hat registry when desired.
3. If patch tags *are* intended on quay.io, consider adding/adjusting documentation in this repo to explicitly state that quay.io supports `x.y.z` tags for `plugin-catalog-index` so users and downstream automation rely on the right contract.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}