charts: fix chart version and appVersion #1620
Closed
Conversation
This file contains hidden or 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
Signed-off-by: Jakob Hahn <jakob.hahn@hetzner.com>
|
According to the current release process those are bumped here |
|
@marcofranssen but they were not bumped in the release as I was trying to explain. The current branch release-3.4 DOES NOT INCLUDE THE CHANGES for the chart. https://github.com/fluent/fluent-operator/blob/release-3.4/charts/fluent-operator/Chart.yaml This PR is targeting the branch you are referencing ... |
|
You can compare it to the release-3.3 and see the difference. In the branch all the versions are correctly set to 3.3.0 but for 3.4.0 they are not. |
This was referenced May 20, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What this PR does / why we need it:
The current v3.4.0 release is not usable with HELM as the version and appVersion of the chars were not updated.
Once this is merge the tag v3.4.0 should be forced pushed with those changes to fix the current release. Otherwise a v3.4.1 is needed.
Related to #1619
Which issue(s) this PR fixes:
Fixes #
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: