fix(infra): Update chart releaser

[justin-tahara]

Description

[Provide a brief description of the changes in this PR]
The chart releaser did not have the kedacore chart so it failed to build

How Has This Been Tested?

[Describe the tests you ran to verify your changes]
Will run in CI

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)
• [Optional] Override Linear Check

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
internal-search	Building	Preview	Comment	Sep 16, 2025 11:58pm

[greptile-apps]

Greptile Summary

This PR fixes a build failure in the Helm chart release workflow by adding the missing KEDA repository configuration. The onyx-stack Helm chart declares a dependency on KEDA version 2.17.2 from the kedacore repository in its Chart.yaml, but the helm-chart-releases.yml workflow was only configured to add bitnami and onyx-vespa repositories during the chart building process.

The fix adds helm repo add keda https://kedacore.github.io/charts to the "Add required Helm repositories" step in the release workflow, ensuring that all chart dependencies can be resolved during the build process. This brings the chart releaser workflow in line with the chart's actual dependencies and prevents build failures when Helm attempts to fetch the KEDA chart dependency.

The change is minimal and surgical, affecting only the repository configuration step without modifying any chart logic or deployment configurations. It also includes a formatting improvement by adding a trailing newline to the file.

Confidence score: 5/5

• This PR is extremely safe to merge with virtually no risk of causing issues
• Score reflects a simple, well-targeted fix that directly addresses a clear build failure with minimal scope
• No files require special attention as this is a straightforward infrastructure configuration fix

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[cubic-dev-ai]

No issues found across 1 file