Unlike ClassPathBeanDefinitionScanner, RepositoryComponentProvider does not override getRegistry() so it will always return null. This means that any condition evaluation that's performed as a result of the scanning will be done without a BeanFactory available from the ConditionContext.
In the context of Spring Boot, this arrangement has previously meant that any condition evaluation that's performed won't be added to the condition evaluation report. Due to some nullable changes in Spring Framework it now means that a failure occurs. I'm not sure that's right, and will raise an SPR ticket, but it would be good to fix this regardless so that any condition evaluation can be added to the report