Update subcharts and release config #222
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses
when calling
helm dependency update.The latter is actually of importance when updating the subchart versions to create a valid
Chart.lock.However, we lately didn't update the subchart versions and just bumped the umbrella chart.
There are also no public releases of the subcharts.
While for the server this is debatable, the
agentchart is actually interesting as this one could be deployed standalone in a meaningful way.Maybe we should maintain all of them at the same hierarchy level and rename the
woodpeckerchart towoodpecker-stack?