Network Imaging a machine with 9.1 repos is automatically installed with 9.2

Apologies as this is happening with Rocky, but as it's downstream, I'm thinking it would be the same issue with Redhat and we do pay for Redhat licensing. The Rocky Wiki says Redhat removed the updates repo (except for Fedora) and now new packages go into the base and appstream repos.

I had a kickstart set up and it was imaging machines with 9.1, but as soon as 9.2 came out a couple of weeks ago anything I network image after that is 9.2.

I tried excluding the 9.2 kernels from the repos and 9.1 kernels did indeed install, but I still end up with a 9.2 image. I'm assuming the install image from 9.2 gets used. I did notice I was forced to add the baseOS 9 after the update and before that just having 9.1 was sufficient to successfully complete imaging. I'm assuming a bunch of packages were removed from 9.1 and ended up in 9. This would be an easy fix I think if I were able to set repo priority in kickstart, but sadly that option doesn't exist.

We have about 1000 linux machines and I'm hoping this isn't going to be how things are from now on, since we typically test for a long period of time in our complex environment and I need to be able to lock in a version.

Is there a workaround to this behaviour?

In Redhat 7 I was just able to exclude the now defunct "updates" repo and the version I wanted got installed. If I had updates repo included in the kickstart then it would behave this way and install the latest minor version.

Thanks for any help.