[release-1.10] fix: pin catalog index tag to 1.10.2

[openshift-cherrypick-robot]

This is an automated cherry-pick of #271

/assign rm3l

[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

Pin plugin catalog index image to 1.10.2 on release-1.10

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Pin plugin catalog index image from floating 1.10 tag to 1.10.2 for stability.
• Document the temporary pin with bug references (RHDHBUGS-3455, RHDHBUGS-3492).
• Normalize env file ending by ensuring the last variable has a trailing newline.

Diagram

graph TD
  Env["default.env"] --> App["RHDH (Backstage)"] --> Catalog["Plugin catalog index"] --> Image["quay.io tag 1.10.2"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Pin by immutable digest (sha256) instead of tag

• ➕ Eliminates risk of tag mutation/re-pointing entirely
• ➕ Improves reproducibility and supply-chain traceability
• ➖ Operational overhead to update digests for each release
• ➖ Harder for humans to quickly identify the version without extra tooling

2. Fix/restore the floating 1.10 tag upstream

• ➕ Keeps configuration simpler (no per-patch pinning)
• ➕ Aligns with expected semver/tagging behavior for consumers
• ➖ Requires coordination and remediation in the image publishing pipeline
• ➖ Doesn’t immediately unblock this release branch if upstream takes time

3. Add a release-branch override mechanism (e.g., separate env for release)

• ➕ Keeps stable defaults while allowing quick hotfix pins per branch/environment
• ➕ Reduces chance of future accidental drift in shared defaults
• ➖ More configuration surface area and potential for divergence
• ➖ May be overkill for a temporary issue

Recommendation: Keep this PR’s approach for the release-1.10 branch to quickly restore stability. If the issue persists or recurs, prefer pinning by digest for immutability and/or fixing the upstream 1.10 tag publishing so consumers can safely use the floating minor tag again.

Files changed (1) +3 / -2

Other (1) +3 / -2

default.envPin catalog index image tag to 1.10.2 and document temporary workaround +3/-2

Pin catalog index image tag to 1.10.2 and document temporary workaround

• Updates CATALOG_INDEX_IMAGE from the floating 1.10 tag to the pinned 1.10.2 tag, with a TODO comment referencing the tracking bugs. Also ensures NOTEBOOKS_QUERY_PROVIDER_ID remains intentionally empty while restoring a proper trailing newline at EOF.

default.env

[rhdh-qodo-merge]

Code Review by Qodo

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

Context used

✅ Cross-repo context

  Explored: repo: redhat-developer/rhdh (branch: release-1.10, sha: da65cdf8)

  Explored: repo: redhat-developer/rhdh-plugins (sha: 70f61dab)

1. Catalog index tag drift 🔗 Cross-repo conflict ☼ Reliability

Description

This repo now defaults CATALOG_INDEX_IMAGE to quay.io/rhdh/plugin-catalog-index:1.10.2 while
compose.yaml still defaults RHDH_IMAGE to the floating :1.10 tag; if that resolves to RHDH
1.10.3 (current in rhdh release-1.10), rhdh-local will run with an older catalog index/default
plugin config than rhdh’s release version expects/publishes.

Code

default.env[R16-17]

+# TODO: Pinned due to issues with the floating 1.10 tag - see RHDHBUGS-3455 and RHDHBUGS-3492
+CATALOG_INDEX_IMAGE=quay.io/rhdh/plugin-catalog-index:1.10.2

Relevance

⭐⭐ Medium

Team updates image tags, but has recent disagreement on catalog index tag timing; alignment change
is nontrivial.

PR-#205
PR-#164

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The PR pins CATALOG_INDEX_IMAGE to 1.10.2, while rhdh-local still defaults the main app image to
the floating :1.10 tag. In the rhdh repo (release-1.10 snapshot), the application version is
1.10.3, and rhdh’s workflow derives the plugin-catalog-index tag directly from that
version—indicating the “matching” catalog index for the release line has moved past 1.10.2.

default.env[14-18]
compose.yaml[24-30]
External repo: redhat-developer/rhdh, package.json [1-4]
External repo: redhat-developer/rhdh, .github/workflows/update-dynamic-plugins-default.yaml [39-71]
External repo: redhat-developer/rhdh, .ci/pipelines/trigger-nightly-job.sh [101-109]

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` pins the catalog index image to `1.10.2`, but the default RHDH image in `compose.yaml` is still the floating `1.10` tag. In the rhdh repo, the catalog index tag used/updated for a release line is derived from the rhdh `package.json` version (currently `1.10.3` on release-1.10), so rhdh-local may drift from the intended “matching” catalog index for the RHDH patch version it actually runs.

## Issue Context
- If the goal is to work around known issues in the floating `1.10` catalog index tag, consider also pinning `RHDH_IMAGE` to the same patch level (if available), or update `CATALOG_INDEX_IMAGE` to match the current patch that rhdh publishes for release-1.10.
- If pinning is intentional, document the supported version skew explicitly (and consider adjusting CI image-selection logic so rhdh-local tests remain representative).

## Fix Focus Areas
- default.env[14-18]
- compose.yaml[24-30]

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

---