radar-hub: stage 1.9.0-rc.4 (Hub 1.9.0-rc.4)

[hisco]

Stages Hub 1.9.0-rc.4. The chart templates are unchanged from 1.9.0-rc.3; only version and appVersion move.

Hub 1.9.0-rc.4 adds "Move it for me" through a move request the hub registers with Radar Cloud (skyhook-dev/radar-hub#279, skyhook-dev/radar-hub-web#334). It works on hubs without a public address. Radar Cloud already runs the matching backend and web.

Merge only after ghcr.io/skyhook-dev/radar-hub:1.9.0-rc.4, ghcr.io/skyhook-dev/radar-hub-web:1.9.0-rc.4 and ghcr.io/skyhook-dev/radar-hub-ai-agent-sandbox:1.9.0-rc.4 are published. Merging publishes the chart. As a pre-release, it isn't the default for helm install.

Testing: tests/render-matrix.sh all checks pass, helm lint with ci/test-values.yaml passes.

---

Note

Low Risk
Metadata-only chart version bump with no Kubernetes manifest or configuration changes.

Overview
Bumps the radar-hub Helm chart from 1.9.0-rc.3 to 1.9.0-rc.4 by updating version and appVersion in Chart.yaml. No template or values changes—this release tracks Hub 1.9.0-rc.4 images (hub, web, ai-agent-sandbox) once they are published.

Merge is gated on those container images being available; merging publishes the chart as a pre-release (not the default helm install target).

^{Reviewed by Cursor Bugbot for commit 163030c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Stage Radar Hub Helm chart 1.9.0-rc.4

⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Bump the chart and Hub application versions to 1.9.0-rc.4 without changing templates.
• Stage the release candidate for publication after the matching Hub, web, and sandbox images are
 available.

High-Level Assessment

Changing only Chart.yaml is appropriate: the existing templates already default Hub and web image tags to appVersion. No chart behavior needs to change; verify all three required images are published before merging, since merging publishes the chart.

Files changed (1) +2 / -2

Other (1) +2 / -2

Chart.yamlAdvance chart and Hub versions to 1.9.0-rc.4 +2/-2

Advance chart and Hub versions to 1.9.0-rc.4

• Changes both version and appVersion from 1.9.0-rc.3 to 1.9.0-rc.4. The new appVersion becomes the default Hub and web image tag when those tags are not explicitly set.

charts/radar-hub/Chart.yaml

[qodo-free-for-open-source-projects]

Code Review by Qodo

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

1. Web installs the older chart 🔗 Cross-repo conflict ≡ Correctness

Description

The chart now publishes as 1.9.0-rc.4, but radar-hub-web still hard-codes 1.9.0-rc.3 for its
one-cluster installation commands. Users generating that installation from the matching web release
continue deploying the previous chart instead of the Hub rc.4 chart and its rc.4 image selection.

Code

charts/radar-hub/Chart.yaml[R5-10]

+version: 1.9.0-rc.4
# The Hub release this chart installs. image.hub.tag and image.web.tag both
# default to it when unset. Deliberately independent of `version` above — see
# README.md. Rewritten by the release job in skyhook-dev/radar-hub; do not carry
# a version number in this comment, it will go stale.
-appVersion: "1.9.0-rc.3"
+appVersion: "1.9.0-rc.4"

Evidence

The PR changes both chart version and appVersion to rc.4, while the related web repository's
generated one-cluster installation flow still selects chart rc.3 and tests assert that value. These
repositories therefore disagree on the chart version used by the self-hosting installation
experience.

helm-charts -> radar-hub-web
charts/radar-hub/Chart.yaml[5-10]
External repo: skyhook-dev/radar-hub-web, src/pages/settings/SelfHosting.tsx [2440-2443]
External repo: skyhook-dev/radar-hub-web, src/pages/settings/SelfHosting.oneCluster.test.ts [90-100]

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 chart is being staged as `1.9.0-rc.4`, while radar-hub-web still pins its one-cluster installation artifacts to `1.9.0-rc.3`. This leaves the cross-repository installation flow selecting the previous chart release.

## Fix Focus Areas
- charts/radar-hub/Chart.yaml[5-10]
- /cross_repos/radar-hub-web/src/pages/settings/SelfHosting.tsx[2440-2443]
- /cross_repos/radar-hub-web/src/pages/settings/SelfHosting.oneCluster.test.ts[90-100]

## Recommended Fix
Coordinate the radar-hub-web release by updating `ONE_CLUSTER_CHART_VERSION` and its expected generated-command tests to `1.9.0-rc.4`, or explicitly retain the rc.3 pin only if that is the intended release contract. Publish the matching web image before merging the chart release as required by the release process.

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

---

Context sources

✅ Compliance rules (platform): 1 rule

✅ Cross-repo context — repo relationships

  Explored: repo: skyhook-dev/radar-hub-web (sha: 35eada1f) — View relationship

  Explored: repo: skyhook-dev/radar-hub (sha: 81754a41) — View relationship

Review mode: 🚀 Fast: This is a localized, self-contained Helm chart metadata version bump with no template or runtime logic changes.

Tip of the day

💡 Did you know, you can turn on the rule miner and Qodo learns your standards from review history

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

1. Web installs the older chart 🔗 Cross-repo conflict ≡ Correctness

The chart now publishes as 1.9.0-rc.4, but radar-hub-web still hard-codes 1.9.0-rc.3 for its
one-cluster installation commands. Users generating that installation from the matching web release
continue deploying the previous chart instead of the Hub rc.4 chart and its rc.4 image selection.

Agent Prompt

## Issue description
The chart is being staged as `1.9.0-rc.4`, while radar-hub-web still pins its one-cluster installation artifacts to `1.9.0-rc.3`. This leaves the cross-repository installation flow selecting the previous chart release.

## Fix Focus Areas
- charts/radar-hub/Chart.yaml[5-10]
- /cross_repos/radar-hub-web/src/pages/settings/SelfHosting.tsx[2440-2443]
- /cross_repos/radar-hub-web/src/pages/settings/SelfHosting.oneCluster.test.ts[90-100]

## Recommended Fix
Coordinate the radar-hub-web release by updating `ONE_CLUSTER_CHART_VERSION` and its expected generated-command tests to `1.9.0-rc.4`, or explicitly retain the rc.3 pin only if that is the intended release contract. Publish the matching web image before merging the chart release as required by the release process.

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

[hisco]

Not needed: the chart is unchanged from 1.9.0-rc.3. Hub images are being tested on a test hub via an image-tag override, then 1.9.0 GA will be staged instead.