How to resolve a conflict in dependency version in a nuget package?

We're developing a class library that's being packaged as nuget. That library has a dependency on Unity.Container. We're distributing this library to be used by a couple of other projects of other teams. Those projects both uses Unity.Container. But the problem is that one of the projects uses an older version of Unity and updating/changing version is not an option for both projects.

1. How can I package my nuget library in a way that we can satisfy the version of both projects?

The only thing we're using in Unity.Container are just the basics, RegisterType, RegisterInstance and Resolve.

2. Is there a design pattern that will totally eliminate the need to add Unity.Container as a dependency in our nuget package?