Skip to content

feat(request-node): update to 0.49.0 #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

feat(request-node): update to 0.49.0 #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charts/request-node/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
apiVersion: v2
appVersion: 0.47.0
appVersion: 0.49.0
Copy link
Copy Markdown

@greptile-apps greptile-apps Bot May 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 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?

description: A Helm chart for Request Node
name: request-node
version: 0.9.0
Copy link
Copy Markdown

@greptile-apps greptile-apps Bot May 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 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.

Expand Down