-
Notifications
You must be signed in to change notification settings - Fork 42
Fix helm pins on release branch #809
New issue
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
Merged
Merged
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: Tiago Castro <tiagolobocastro@gmail.com>
Abhinandan-Purkait
approved these changes
Jan 9, 2026
niladrih
approved these changes
Jan 13, 2026
Member
Author
|
bors merge |
bors-openebs-mayastor bot
pushed a commit
that referenced
this pull request
Jan 13, 2026
809: Fix helm pins on release branch r=tiagolobocastro a=tiagolobocastro <! Co-authored-by: Tiago Castro <tiagolobocastro@gmail.com>
Contributor
|
Build failed: |
Member
Author
hmm bors merge |
bors-openebs-mayastor bot
pushed a commit
that referenced
this pull request
Jan 13, 2026
809: Fix helm pins on release branch r=tiagolobocastro a=tiagolobocastro <! Co-authored-by: Tiago Castro <tiagolobocastro@gmail.com>
Member
Author
|
bors merge |
Contributor
|
Already running a review |
Contributor
|
Build failed: |
8615c5c to
34f8ee6
Compare
Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
34f8ee6 to
e17e08e
Compare
Member
Author
|
bors merge |
Contributor
|
Build succeeded:
|
Member
Author
|
@mergify backport develop |
✅ Backports have been createdDetails
|
7 tasks
bors-openebs-mayastor bot
pushed a commit
that referenced
this pull request
Jan 14, 2026
811: Fix helm pins on release branch (backport #809) r=tiagolobocastro a=mergify[bot] ## Description ## Motivation and Context ## Regression ## How Has This Been Tested? ## Types of changes - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [ ] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added unit tests to cover my changes.<hr>This is an automatic backport of pull request #809 done by [Mergify](https://mergify.com). Co-authored-by: Tiago Castro <tiagolobocastro@gmail.com>
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.
Description
Motivation and Context
Regression
How Has This Been Tested?
Types of changes
Checklist: