This is potentially a breaking change if people have sizes in their database that are specified incompletely against the hardware, e.g. if they have a size with only memory and core constraint and the hardware is reported by the metal-hammer with disks. With this change the size will not be matched anymore and the storage constraint matching the reported hardware needs to be added.
The reported hardware is now exhaustively checked against the size constraints. In general this implies that core, memory and storage constraints always need to be specified in the size constraints. If this is missing in any of your defined sizes, please adapt those accordingly.
This is potentially a breaking change if people have sizes in their database that are specified incompletely against the hardware, e.g. if they have a size with only memory and core constraint and the hardware is reported by the metal-hammer with disks. With this change the size will not be matched anymore and the storage constraint matching the reported hardware needs to be added.