We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is proposing a workflow improvement for chart maintainers - increment Chart.yaml version when updating values.yaml
Given the following values.yaml:
apiVersion: v1 appVersion: "1.0" description: inlets-operator for Kubernetes name: inlets-operator version: 0.17.9 keywords: - networking - loadbalancer - ingress - selfhosting - tunnels - inlets
I'll see new images put into values.yaml, from arkade chart upgrade, but the Chart.yaml always needs bumping too and that's a manual task.
arkade chart upgrade
I'd suggest always bumping the minor patch version, and if it's a bigger change the user can just edit the file.
arkade chart bump
In the case of OpenFaaS, if 6 repos change then I have to edit 6 files manually.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
This is proposing a workflow improvement for chart maintainers - increment Chart.yaml version when updating values.yaml
Expected Behaviour
Given the following values.yaml:
I'll see new images put into values.yaml, from
arkade chart upgrade
, but the Chart.yaml always needs bumping too and that's a manual task.I'd suggest always bumping the minor patch version, and if it's a bigger change the user can just edit the file.
Current Behaviour
In the case of OpenFaaS, if 6 repos change then I have to edit 6 files manually.
The text was updated successfully, but these errors were encountered: