It looks like the cockpit-composer v40 and v41 updates are missing from f37, possibly due to a configuration error in packit. The upcoming release of Fedora should not have an older version than other Fedora branches, and currently the package will be downgraded from v41 to v39 on upgrade from Fedora 36 to 37. Please make sure to create the missing build / update.
Confirmed, fedora-37 is missing in https://github.com/osbuild/cockpit-composer/blob/main/packit.yaml
F37 support is already in the works: https://github.com/osbuild/cockpit-composer/pull/1568
Isn't that kind of a brittle setup, requiring to manually update the list of target Fedora releases every few months? As of right now, Fedora 37 will release with an outdated version of this package ... so either way, you should really merge the changes from Rawhide or F36 into the f37 branch and submit the missing builds / updates, independent of the work to enable the F37 target in the packit configuration.
You can of course opt into "fedora-stable" as an alias [1]. We don't do that in cockpit as we always just want to support the two most recent releases -- e.g. we don't want to release to F35 any more. But c-composer is entirely free to set that policy by itself. [1] https://packit.dev/docs/configuration/#aliases
FEDORA-2022-bfb7b86f9a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bfb7b86f9a
FEDORA-2022-bfb7b86f9a has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-bfb7b86f9a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-bfb7b86f9a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-bfb7b86f9a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.