-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Release v2.8.2 #4132
Comments
Is it okay if we backport all of those in one PR? I started cherrypicking into one branch, but I am wondering if it is okay. |
|
I think it's not a problem @kedacore/keda-core-contributors ? |
I opened #4135 where I am back porting all PRs except the three last ones from the table above. #4012 is specially tricky because it is using a lot of new code from APIs that I suppose was refactored. So since I am not 100% familiar with the code base I feel not safe to cherrypick. I will work on the issues I see already in #4135 and will try to make CI work. If you or another maintainer could help, would be nice. Thx. |
No worries, if you have cherry-picked the others, we can fix those 3. You have already helped a lot, with the amount of commits you have backported 🙇 |
okay, let's proceed with #4006 in a separate PR once this one is merged |
Yeah, I'll back port that PR, I did the original PR so I hope it'll be easy :) |
KEDA v2.8.2 has been released 🥳 🥳 🥳 BTW, thanks a ton for your awesome help ❤️ |
Due to the reduced k8s versions supported for KEDA v2.9, we have decided to do an exceptional release for v2.8, back porting all the fixes and CVEs we have already solved.
This issue will track all the needed PR for being back ported:
Additionally, we need to solve this issue during the release, fixing the v2.8 helm chart
The text was updated successfully, but these errors were encountered: