This is inherently contradictory with the trunk-based development model. I get the feeling you need to pin to v1.4 but ideally by being on the trunk head at al

This is inherently contradictory with the trunk-based development model. I get the feeling you need to pin to v1.4 but ideally by being on the trunk head at all times, you force everyone (especially the library owners, and yourself, by writing tests around your wrapper) to do things properly such as having enough tests in place. Otherwise, you find yourself digging a grave for yourself when the time comes to migrate from v1.4 to v1.7, and it becomes grunt work that nobody wants to take on.