Adding an interface to a package is at least a minor change (1.2.3 -> 1.3.0) since you break the provider of the API (which in OSGi is a package), providers of an API have virtually no backward compatibility since they, well, provide the API. After all, any new obligation in the API requires some new code.
Now assume you put an obligation on the consumer to implement this new interface in the API. This change (not visible to the compiler) obviously breaks all existing consumers and will therefore be a breaking change for everybody (e.g. 1.2.3 -> 2.0.0).
To conclude:
- Micro change -> backward compatible with existing providers and consumers of the API
- Minor change -> existing providers of the API are not compatible but consumers are
- Major change -> existing providers and consumers are no longer compatible