feat(request-node): update to 0.49.0

[github-actions]

Automated changes by create-pull-request GitHub action

[greptile-apps]

Greptile Summary

This automated PR bumps appVersion in the request-node Helm chart from 0.47.0 to 0.49.0, reflecting an upstream application release. The chart's own version field is left unchanged at 0.9.0.

• The chart version field was not incremented alongside appVersion. Helm repository indexes are keyed on version, so chart consumers will not see a new entry and will continue pulling the previous image tag.
• appVersion skips 0.48.x entirely — it is worth confirming whether that release series required a separate chart update.

Confidence Score: 3/5

The chart version was not incremented, so Helm repository consumers will not detect this as a new release and will continue deploying the old image tag.

The only change is an appVersion bump, but the chart version field was left at 0.9.0. Helm repo indexes are keyed on chart version, so downstream users running helm repo update will never see a new entry and the intended application upgrade will silently not happen for anyone consuming this chart through a repo index.

charts/request-node/Chart.yaml — the chart version field needs to be bumped to publish the update correctly.

Important Files Changed

Filename	Overview
charts/request-node/Chart.yaml	Bumps appVersion from 0.47.0 to 0.49.0 (skipping 0.48.x) but leaves chart version at 0.9.0, which will prevent Helm repo consumers from detecting the update.

Sequence Diagram

sequenceDiagram
    participant GHA as GitHub Actions Bot
    participant Chart as Chart.yaml
    participant HelmRepo as Helm Repository Index
    participant Consumer as Chart Consumer

    GHA->>Chart: Update appVersion 0.47.0 → 0.49.0
    Note over Chart: version stays 0.9.0

    Consumer->>HelmRepo: helm repo update
    HelmRepo-->>Consumer: "index entry version=0.9.0 (unchanged)"
    Note over Consumer: No new chart detected ⚠️

    alt If chart version had been bumped (e.g. 0.9.1)
        HelmRepo-->>Consumer: "index entry version=0.9.1 (new)"
        Consumer->>Consumer: helm upgrade → deploys appVersion 0.49.0 ✅
    end

Loading

_{Reviews (1): Last reviewed commit: "feat(request-node): update to 0.49.0" | Re-trigger Greptile}

[greptile-apps]

Chart version not bumped alongside appVersion

The chart version field is still 0.9.0 despite appVersion changing from 0.47.0 to 0.49.0. Helm chart repositories (e.g. ChartMuseum, OCI registries, GitHub Pages via helm repo index) use the version field — not appVersion — to detect new releases. If version stays the same, downstream consumers polling the repo index will not see a new chart entry and will keep deploying the old image tag.

[greptile-apps]

Version jump skips 0.48.x

appVersion advances from 0.47.0 directly to 0.49.0, skipping 0.48.x. Was 0.48.x intentionally omitted (e.g. it was a short-lived patch series), or should there be a separate chart update for it? Was 0.48.x intentionally skipped, or was there a missing chart update for it?