Spring Injection points with wildcards are not as lenient as before

Consider the following interface:

interface SessionRepository<S extends Session> {}

Use as an injection point as follows:

@Configuration
class TestConfiguration {

  @Bean
  SessionEndpoint sessionEndpoint(SessionRepository<? extends Session> sessionRepository) { ... }
}

Work in 6.2.x makes this fail. ResolvableType on the actual instance, resolves SessionRepository as SessionRepository<?>. The current signature looks a bit odd and the repetition of the generic constraints are unnecessary but this didn't use to be a problem.