“Our use case is we build execution environments with specific collection versions in them.
We have a "stable" (semver) version of the EE, used for production job templates, and then we have a "weekly" build version of the EE, containing the latest collections, which we use on some test jobs or lower environments.

We also have a scheduled job that runs every 3 days and syncs all remotes.

This does not really work, as we never know which versions a weekly build contains (unless we check the output of the job), or if the EE causes issues, we don't know which collection update could have caused it.

A better approach would be an event triggered and gitops approach, the event being a notification that a "watched" collection has a new version available.
This would trigger a post on our teams channel, an update to our gitops config as code, changing the collection desired version in the "nightly" build version, which would trigger the rebuild of the "nightly" EE.

This would enable us to track which collection updated cases an issue and also have a clear trail of what has been updated and why, and an overall picture of what all the collection versions inside an EE.
Then finally we can rollout this new EE to all the rest of the jobs, based on a schedule.

Alternatively, we could write our own software that uses the API endpoint below and checks the versions on regular basis, and calls EDA endpoint

curl -X 'GET' \
  'https://galaxy.ansible.com/api/_ui/v1/collection-versions/?name=mysql&namespace=community' \
  -H 'accept: application/json'

url = "https://console.redhat.com/api/automation-hub/_ui/v1/collection-versions/"”