When this is necessary, we have the migrations versioned independently of the services that consume the database; essentially, there is a "database package" and

When this is necessary, we have the migrations versioned independently of the services that consume the database; essentially, there is a "database package" and a database schema version. We try our best to make all changes additive, to reduce the potential for breaking changes that may require all consumers (your services) to change. As I'm sure others will comment, you should do everything you can to eliminate these dependencies; ideally, the database<-->service relationship should be 1-1 and not 1-many.