Thanks @jensens! Indeed, pinning plone.supermodel to >= 1.6.0 fixed the problem
Plone Foundation Code of Conduct