chore(ci): revert version changes in release pipeline #402
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
khvn26
approved these changes
Jul 25, 2025
Member
khvn26
left a comment
khvn26
left a comment
There was a problem hiding this comment.
We probably need a GH issue to sort the Helm versions in CI later.
Contributor
Author
|
matthewelwell
deleted the
chore(ci)/revert-version-changes-in-release-pipeline
branch
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.
Thanks for submitting a PR! Please check the boxes below:
Changes
This PR reverts most of the version changes that were bundled into this PR in order to fix the issue seen in the release action after merging the latest PR from release please here.
How did you test this code?
I updated the workflow to run on pushes from this branch, and commented out the actual release section that would fail without being triggered by a tag. The successful run (at least to confirm that the issue seen in the above linked job is resolved) can be seen here.