Decide how to implement planned breaking changes - as one consolidated release or as a series of incremental releases.
The changes are
MODINVSTOR-135: Add FK constraints to instance/holdings_record/item
MODINVSTOR-171: Make instance.edition repeatable ( -> instance.editions ) (+ MODINV-78, MODCXINV-32, UIIN-299)
MODINVSTOR-173: Make HRID required
MODINVSTOR-180: Remove property instance.urls (replaced by instance.electronicAccess) (+ MODINV-81, MODCXINV-34, UIIN-303)
MODINVSTOR-186: Remove property instance.catalogingLevelId and reference end-point `cataloging-levels` (duplicate of instance status) (+ MODINV-82, UIIN-312(done) )
MODINVSTOR-191: Rename electronicAccess.relationship to relationshipId (changes from free-text to UUID) (+ MODINV-84)
MODINVSTOR-195: Make instance.formatId repeatable ( -> instance.formatIds ) ( MODINV-86, MODCXINV-35, UIIN-330)
Our Ansible build process seem to be ready for these changes, ref. FOLIO-1499
Otherwise the changes will require updates of dependencies in mod-codex-inventory, mod-inventory, ui-inventory, ui-checkout, ui-checkin, ui-requests, mod-circulation.
In the first four comments I've tried to out-line the required dependency updates and code changes - if we do them one at a time, each with a major update to mod-inventory-storage, or do them all together in one major release of mod-inventory-storage.