Patterns to segregate Models and DbContext on ASP.NET Core microservices

I'm trying to make my services to deploy individually without depending on each other.

All services will be using the same SQL database using EF Core (same DbContext).

I'm using a separate project (MyServices.Data) that has all my models and the DbContext, but I'm really dependent on this and if there is any change on this Data project, all services needs to be redeployed.

Is there any pattern/approach to this situation so I can have my project not dependant on it?