Please note that bodhi-client-6.0 was already pushed to F36. Just for info. It is true that the update is backwards-incompatible, but at the same time the server was updated as well, so I didn't see as a breach of our stable updates policy.
I disabled the time-based move to stable (which I should have done for F36). This one can wait for packit to update if it does not break your code too @kparal?
I'm happy to help the packit folks upgrade their client usage, if they want.
For my defense, I've announced this change almost 3 months ago on devel and devel-announce. But I do apologize for the trouble it's causing. Bodhi is complex piece to upgrade because you don't want to risk breaking it right before or right after a release.
We've just merged the initial support and we'll release it by the end of this week. We can coordinate our bodhi updates afterwards :) @nforro handles releases this week.
@abompard you are right about the heads-up and we're grateful that we could engage with you and be up to date with information back then. The surprises here for us were:
It's being done in 3 months and not 6 as the thread promised
it's happening in stable and not just rawhide
no reminder on fedora-devel
Bodhi is complex piece to upgrade because you don't want to risk breaking it right before or right after a release.
Completely understand and also can see that issues are popping up with the new authentication mechanism. Thank you for resolving them so promptly.
This update can be pushed to stable now if the maintainer wishes
This update's test gating status has been changed to 'waiting'.
This update has been submitted for testing by bodhi.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
using it from fedora-easy-karma right now to submit this comment
abompard edited this update.
Has backwards incompatible API changes within a stable Fedora release.
This update would break package packit due to the API change.
https://github.com/packit/packit/issues/1624
Please wait at least a week with pushing it so we can support the OIDC auth mechanism.
Please note that bodhi-client-6.0 was already pushed to F36. Just for info. It is true that the update is backwards-incompatible, but at the same time the server was updated as well, so I didn't see as a breach of our stable updates policy.
I disabled the time-based move to stable (which I should have done for F36). This one can wait for packit to update if it does not break your code too @kparal?
I'm happy to help the packit folks upgrade their client usage, if they want.
For my defense, I've announced this change almost 3 months ago on devel and devel-announce. But I do apologize for the trouble it's causing. Bodhi is complex piece to upgrade because you don't want to risk breaking it right before or right after a release.
We've just merged the initial support and we'll release it by the end of this week. We can coordinate our bodhi updates afterwards :) @nforro handles releases this week.
@abompard you are right about the heads-up and we're grateful that we could engage with you and be up to date with information back then. The surprises here for us were:
Completely understand and also can see that issues are popping up with the new authentication mechanism. Thank you for resolving them so promptly.
This update can be pushed to stable now if the maintainer wishes
Thank you for waiting for us. We have just released an update of packit that works with both versions of bodhi: 5 and 6: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5b3327ff5e
@abompard Time to push this?
This update has been submitted for stable by abompard.
This update has been pushed to stable.