Forked projects are now unable to run CI in MRs to projects with access to premium runners

We have a premium plan on Gitlab.com and therefore have access to different runners. We have configured CI in some of our projects to use these runners: saas-linux-large-aarch64 and saas-linux-large-amd64

Starting today / a few hours ago, people who fork our projects are unable to execute CI on MRs originating from their forks, e.g. https://gitlab.com/user0-tb/pmaports/-/jobs/7766825351

It seems like maybe this is due to some recent internal change in gitlab.com(?) (cc @tmaczukin)