TBCH it would already help if the releases of ORM would be slightly more predictable and would adhere to semantic versioning in user facing APIs.

• 5.0.9 broke stored procedure support ( HHH-10515 Complete ), which is still broken in 5.1.0 and 5.2.0.
• 5.1 appeared without a milestone or release candidate, broke some pretty fundamental JPA things e.g HHH-10514 Complete .
• basically everyone is waiting for 5.1.1 as the aforementioned issues were scheduled to be released in that version, but it's overdue for 3 month now with any notice whatsoever
• then all of a sudden 5.2 appears without milestone or release candidate, the requirement to upgrade to Java 8 (a 6.0 thing if you followed semver), broken binary compatibility in org.hibernate.Query (a 6.0 thing if you followed semver) and JPA specification violations ( HHH-10803 Complete )

With something like this in place it's close to impossible to build downstream components in a reliable way. I can definitely understand you want to cut of everything before 5.0 but that particular train is tricky to work with to phrase it politely.