Guillaume Smet
Guillaume Smet
So there are some thoughts about how to handle things here: https://docs.quarkiverse.io/quarkus-github-action/dev/push-to-production.html but as you have experienced it, the situation is far from being ideal... I really think we should...
Yeah sure, and don't feel obliged to anything. If you play with it and find interesting things about it, please post back and if you want to discuss this further,...
@ahus1 we mostly downgraded for you so if you think you want to upgrade, feel free to create a PR. Let's keep this one in core IMO, it's practical and...
I suspect https://github.com/quarkusio/quarkus/pull/47658 but it might also impact the Operator SDK version in the Platform /cc @metacosm Not sure exactly how safe it is to update this in 3.20.
Also, we are sure this upgrade won't break the access to older clusters?
@ashwinik307 :wave: what exactly are you after? If it's CI coverage then it might make sense. I'm not sure about the binaries part though given I don't think we are...
@carlesarnal there are some CI issues that I think are related to your changes. See the reports.
Also we can't switch to a random fork. It needs careful consideration. There have been too many supply chain attacks these past years, we need to be extra careful.
@Karm could you have another look at this one?
Failed to pass quarkus.profile to more than one integration test case when testing native executable
It would probably help if you could take the time to assemble a small test case and post it.