You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently while I added a tool to rename the version folders to the latest version in Chart.yaml, we still have to manually edit each Chart.yaml file to update versions. This is not going to work long-term
Describe the solution you'd like
Add a simple script which we can feed the names of the containers we like to update the versions for (or --all for that mater) and which version we like to increase (major, minor, patch)
Describe alternatives you've considered
Keeping it manual, getting CI to do it
Additional context
Keeping it manual has no future and CI can't push to PR's
The text was updated successfully, but these errors were encountered:
* first work for allowing ramdisk usage
* add bump tooling.
Fixes: #157
* bump minor versions due to adding ramdisk emptydir to persistence
* allow disabling persistent storage
* actually push major as it is breaking in theory
* cleanup hpm example code
* Allow custom storageClass and fix bug using the wrong storageClass
* try fixing gabs
* cleanup
* update tests
* revert some permission job changes
* reverse some of the 3.0 common incompatible bitwarden changes
Is your feature request related to a problem? Please describe.
Currently while I added a tool to rename the version folders to the latest version in Chart.yaml, we still have to manually edit each Chart.yaml file to update versions. This is not going to work long-term
Describe the solution you'd like
Add a simple script which we can feed the names of the containers we like to update the versions for (or --all for that mater) and which version we like to increase (major, minor, patch)
Describe alternatives you've considered
Keeping it manual, getting CI to do it
Additional context
Keeping it manual has no future and CI can't push to PR's
The text was updated successfully, but these errors were encountered: