-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(manager/helmfile): allow forward slashes in OCI chart names #33162
Conversation
bc18120
to
66bf03d
Compare
Issue was described in [discussion][1]. The helmfile manager now properly handles OCI chart names that contain forward slashes. Previously, the validation would reject chart names with slashes even for OCI repositories. This change modifies the isValidChartName function to use different validation rules for OCI vs non-OCI charts. Added test coverage to verify the new behavior works correctly. [1]: renovatebot#26207
66bf03d
to
6040cd7
Compare
@rarkins, my bad; I forgot to check the TS compilation. I checked and fixed both issues. Tests are running too. |
@viceice Hey, I've fixed the tests and linter problems. Could you review it once more? I see that the build passes. Thank you! |
@rarkins I think after my last push a new review is required to pass check and merge PR. |
🎉 This PR is included in version 39.81.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changes
The helmfile manager now properly handles OCI chart names that contain forward slashes. Previously, the validation would reject chart names with slashes even for OCI repositories. This change modifies the isValidChartName function to use different validation rules for OCI vs non-OCI charts.
Added test coverage to verify the new behavior works correctly.
Context
Issue was described in discussion.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: