one other thing you could try here to determine whether it’s a pex bug or environment issue - based on past resolver issues - would be to transitively pin that req in your top level target deps