Other packages affected by this issue:
- https://bodhi.fedoraproject.org/updates/FEDORA-2022-d3a2408f3a
- https://bodhi.fedoraproject.org/updates/FEDORA-2022-9d02441b24
- https://bodhi.fedoraproject.org/updates/FEDORA-2022-850adec1a6
- https://bodhi.fedoraproject.org/updates/FEDORA-2022-274a29eeef
- https://bodhi.fedoraproject.org/updates/FEDORA-2022-9421366d9c
- https://bodhi.fedoraproject.org/updates/FEDORA-2022-74c5276a79

I've fixed some of the above updates, but since there are so many, I'll copy here the instructions I've posted yesterday on devel mailing list, for anyone who wants to self un-stuck their updates:

If your Bodhi update is stuck in the "Pending" state, please make sure
that all the builds inside the update are tagged in the release
candidate tag (which is typically something like
f35-updates-candidate). You can check that by clicking on the build(s)
name(s) in the right column on the update page.

If any build in the update is not properly tagged, you must manually tag
it with something like:

koji tag-build f35-updates-candidate build-0.1.2-1.fc35

(obviously you need koji cli to be installed on your system and you need
to be authenticated with kerberos)

After all the builds in the update are tagged you can push the update to
testing. If you just push the update without all the builds properly
tagged, you'll get another "update ejected from the push" the next Bodhi
composer run.

For updates stuck in the "Testing" state, the quickest solution is to
unpush the update with the button in Bodhi web interface and then
re-submit it to testing.

The underlying issue was resolved, closing.