chore: tagRelease.sh: bump to 1.10.1 in release-1.10 branch [skip-build] [skip-e2e]

[rhdh-bot]

Signed-off-by: rhdh-bot service account rhdh-bot@redhat.com

[rhdh-bot]

/ok-to-test

[github-actions]

⚠️ Files changed in bundle and installer generation!

Those changes to the operator bundle/installer manifests should have been pushed automatically to your PR branch.

NOTE: If the PR checks are stuck after this additional commit, manually close the PR and immediately reopen it to trigger the checks again.

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.10.1-pr-2989-51c15f7
2. https://quay.io/rhdh-community/operator-bundle:0.10.1-pr-2989-51c15f7
3. https://quay.io/rhdh-community/operator-catalog:0.10.1-pr-2989-51c15f7

[nickboldt]

/lgtm
/approve

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

Context used

✅ Compliance rules (platform): 18 rules

1. Missing CSV upgrade path 🐞 Bug ≡ Correctness

Description

The Backstage.io CSV was bumped to v0.10.1 but still provides neither spec.replaces nor an OLM
skipRange, so OLM may be unable to construct an upgrade graph and existing installations may not
see an available update.

Code

bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml[330]

+  version: 0.10.1

Relevance

⭐ Low

Past release bumps for backstage.io CSV omit replaces/skipRange and still merged (e.g., PRs 2146,
2846, 1733).

PR-#2146
PR-#2846
PR-#1733

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The Backstage.io CSV shows version: 0.10.1 but contains no replaces field at the end of spec,
and its metadata.annotations also has no skipRange; meanwhile the RHDH CSV demonstrates the
expected pattern by including both skipRange and replaces for upgradeability.

bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml[313-330]
bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml[3-35]
bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml[51-58]
bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml[448-454]

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 Backstage.io ClusterServiceVersion (CSV) was bumped to `0.10.1`, but it does not declare an OLM upgrade edge (`spec.replaces`) nor a `metadata.annotations.skipRange`. Without one of these, OLM may treat this CSV as a separate upgrade root and not offer upgrades from prior installed versions.

## Issue Context
- RHDH CSVs in this repo include `skipRange` and `replaces`, which establishes a valid upgrade graph.
- The Backstage.io CSV currently ends at `version: 0.10.1` with no `replaces`, and its annotations also lack `skipRange`.

## Fix Focus Areas
- bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml[4-35]
- bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml[313-330]

### Suggested change
Add one of the following (or both, depending on your catalog strategy):
1) `spec.replaces: backstage-operator.v0.10.0` (if the previous CSV is present in the catalog), and/or
2) `metadata.annotations.skipRange: '>=0.0.0 <0.10.1'` (if older bundles are pruned and you want to allow direct upgrades).

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

---

[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 release artifacts to 1.10.1 / 0.10.1 and regenerate operator manifests
⚙️ Configuration changes 🕐 10-20 Minutes

Walkthroughs

Description

• Bump default build/release versions to 1.10.1 (and operator 0.10.1)
• Regenerate Operator CSVs to reflect updated versioning and upgrade paths
• Update install/kustomize manifests to pull the new operator image tag

Diagram

graph TD
R["Release bump 1.10.1"] --> M["Makefile (VERSION)"] --> K["Kustomize profile"] --> I["dist/install.yaml"]
K --> C1["CSV: backstage.io"] --> Q[("quay.io operator image")]
B["CSV base: config/manifests"] --> C2["CSV: RHDH bundle"]

subgraph Legend
  direction LR
  _f["Manifest / config"] ~~~ _img[("Container image")]
end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Single source-of-truth version file

• ➕ Reduces duplicated version fields across Makefile/CSVs/kustomize/dist
• ➕ Lowers risk of partial bumps (e.g., image tag updated but CSV version not)
• ➖ Requires wiring templating/substitution into CSV generation
• ➖ May not align with operator-sdk/OLM expectations for CSV content provenance

2. CI-only regeneration of bundle/dist artifacts

• ➕ Keeps generated artifacts consistent and reproducible
• ➕ Avoids committing frequent timestamp-only churn (createdAt changes)
• ➖ Consumers who rely on repo-committed bundles may be impacted
• ➖ Requires CI changes and an agreed artifact publishing flow

3. Use kustomize/templating to populate replaces/skipRange

• ➕ Automates upgrade-path metadata alongside version bumps
• ➕ Makes it harder to ship incorrect OLM upgrade constraints
• ➖ Adds complexity to release tooling and validation
• ➖ May need custom checks to ensure OLM semantics remain correct

Recommendation: For a release-branch patch bump, the current approach (explicitly updating versions and committing regenerated artifacts) is appropriate and low risk. Longer-term, consider centralizing version metadata (or templating it) to reduce repetitive edits and minimize the chance of mismatched CSV/version/image tags, especially around replaces/skipRange.

File Changes

Other (6)

Makefile Bump default VERSION to 0.10.1 +1/-1

Bump default VERSION to 0.10.1

• Updates the Makefile default VERSION from 0.10.0 to 0.10.1 when VERSION is not provided via environment. This aligns local builds and release tooling with the patch bump.

Makefile

---

backstage-operator.clusterserviceversion.yaml Update backstage-operator CSV to v0.10.1 +4/-4

Update backstage-operator CSV to v0.10.1

• Regenerates the community operator ClusterServiceVersion metadata for the 0.10.1 release. Updates createdAt, CSV name/version, and the referenced operator image tag to quay.io/rhdh-community/operator:0.10.1.

bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml

---

backstage-operator.clusterserviceversion.yaml Update RHDH operator CSV to v1.10.1 and fix upgrade metadata +5/-5

Update RHDH operator CSV to v1.10.1 and fix upgrade metadata

• Regenerates the RHDH operator ClusterServiceVersion for 1.10.1, including a new createdAt timestamp. Adjusts skipRange upper bound to <1.10.1 and updates replaces to rhdh-operator.v1.10.0 to reflect the correct upgrade chain.

bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml

---

backstage-operator.clusterserviceversion.yaml Bump base CSV skipRange/replaces/version to 1.10.1 +3/-3

Bump base CSV skipRange/replaces/version to 1.10.1

• Updates the base CSV used for RHDH manifests so the generated bundle reflects the 1.10.1 release. Specifically bumps skipRange and sets replaces/version to v1.10.0 and 1.10.1 respectively.

config/manifests/rhdh/bases/backstage-operator.clusterserviceversion.yaml

---

kustomization.yaml Point controller image tag to 0.10.1 +1/-1

Point controller image tag to 0.10.1

• Updates the kustomize image transformer to use quay.io/rhdh-community/operator:0.10.1 for the controller image. This drives the tag used in rendered installation artifacts.

config/profile/backstage.io/kustomization.yaml

---

install.yaml Regenerate install manifest to use operator:0.10.1 +1/-1

Regenerate install manifest to use operator:0.10.1

• Updates the rendered install.yaml to pull the controller image quay.io/rhdh-community/operator:0.10.1. This ensures the published install manifest matches the bumped operator release.

dist/backstage.io/install.yaml

---

[rm3l]

/override "PR Publish"

Everything worked, except the last step trying to add a comment to the PR, which, for some reason (unrelated to this PR) failed with 401: https://github.com/redhat-developer/rhdh-operator/actions/runs/27285377188/job/80593498468?pr=2989#step:9:22

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: PR Publish

Details

In response to this:

/override "PR Publish"

Everything worked, except the last step trying to add a comment to the PR, which, for some reason (unrelated to this PR) failed with 401: https://github.com/redhat-developer/rhdh-operator/actions/runs/27285377188/job/80593498468?pr=2989#step:9:22

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.