-
Notifications
You must be signed in to change notification settings - Fork 1k
removes prerelease tag from helm chart #2739
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,27 @@ | ||
| apiVersion: v1 | ||
| entries: | ||
| bifrost: | ||
| - apiVersion: v2 | ||
| appVersion: 1.4.11 | ||
| created: "2026-04-15T18:00:00.000000+00:00" | ||
| description: A Helm chart for deploying Bifrost - AI Gateway with unified interface for multiple providers | ||
| digest: "" | ||
| home: https://www.getmaxim.ai/bifrost | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The |
||
| icon: https://www.getmaxim.ai/bifrost/bifrost-logo-only.png | ||
| keywords: | ||
| - ai | ||
| - gateway | ||
| - llm | ||
| maintainers: | ||
| - email: akshay@getmaxim.ai | ||
| name: Bifrost Team | ||
| name: bifrost | ||
| sources: | ||
| - https://github.com/maximhq/bifrost | ||
| type: application | ||
| urls: | ||
| - https://maximhq.github.io/bifrost/helm-charts/bifrost-2.1.1.tgz | ||
| version: 2.1.1 | ||
| - apiVersion: v2 | ||
| appVersion: 1.4.11 | ||
| created: "2026-04-15T12:00:00.000000+00:00" | ||
|
|
@@ -649,4 +670,4 @@ entries: | |
| urls: | ||
| - https://maximhq.github.io/bifrost/helm-charts/bifrost-1.3.36.tgz | ||
| version: 1.3.36 | ||
| generated: "2026-04-13T12:00:00.000000+00:00" | ||
| generated: "2026-04-15T18:00:00.000000+00:00" | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
value{{- if .value }}is falsy for any empty string, so a user who explicitly setsvalue: ""in theirvalues.yamlwill silently have the field omitted rather than passed to the backend. UsinghasKeyis a more precise guard if the intent is "omit only when the key is absent":For this specific field an empty string and an absent key have the same practical effect (backend auto-generates), so the current behaviour is acceptable — this is a minor suggestion for semantic clarity.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!