Can Liquibase handle this scenario?

• v1.1 has a Table with index i.
• v2.1 contains this table and index as well.

A bug was discovered and in v1.1.0.1 we changes the code and as a result, decided to drop the index.
We created a corresponding patch for v2.1, v2.1.0.6

The customer applied patch v1.1.0.1 and a few weeks later upgraded to v2.1 (without patch 6)

As v2.1 code base performs better with the index we have a "broken" application.

• I can't force my customers to apply the latest patch.
• I can't force the developers to avoid such scenarios.