libvirt has been for weeks in the updates-testing repository. What is happening?
# dnf check-upgrade --enable-repo=updates-testing libvirt\*
Updating and loading repositories:
Repositories loaded.
libvirt-client.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-common.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-config-network.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-interface.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-network.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-nodedev.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-nwfilter.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-qemu.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-secret.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-core.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-disk.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-gluster.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-iscsi.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-iscsi-direct.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-logical.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-mpath.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-rbd.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-scsi.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-driver-storage-zfs.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-kvm.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-lock.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-log.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-plugin-lockd.x86_64 11.0.0-4.fc42 updates-testing
libvirt-daemon-proxy.x86_64 11.0.0-4.fc42 updates-testing
libvirt-libs.x86_64 11.0.0-4.fc42 updates-testing
libvirt-ssh-proxy.x86_64 11.0.0-4.fc42 updates-testing