Hibernate Validator 9.1.0.Final released
by Marko Bekhta
Hello,
We are excited to announce the release of Hibernate Validator 9.1.0.Final.
This series aims to improve performance, introduces new constraints,
applies a new documentation theme, updates dependencies and includes other
improvements.
See our blog for more information:
https://in.relation.to/2025/11/07/hibernate-validator-9-1-0-Final/
See our website for more information about the 9.1 series in general:
https://hibernate.org/validator/releases/9.1/
Have a nice day,
Marko Bekhta
Hibernate Team
marko(a)hibernate.org
11 hours, 38 minutes
- 1
- 0
Hibernate organization membership on GitHub
by Yoann Rodiere
Hello,
As part of the move to Commonhaus, I'm currently going through our GitHub
setup, and I'm noticing we have a lot of users with extensive (and I mean
*extensive*, sometimes admin or even owner) access to our
organization/repositories, but who are no longer regular contributors.
Additionally, we also have organization members on GitHub who are not
technically Hibernate members: they have never actually contributed to
Hibernate, but are there for technical reasons, for example because they're
coworkers who helped out with some infrastructure issue.
While it's fine in principle, because we trust these people, it's very,
very far from security best practices. Account hacking happens, email
addresses get stolen, and the people using these GitHub accounts might one
day be an attacker instead of the person we trust.
According to Commonhaus' automated report, we're currently at 32 people
having admin rights on one Hibernate repository or another. Which I think
we can all agree is much more than necessary.
For that reason, I'd like to propose that:
1. *We create an "Alumni" team in our GitHub organization*, moving to that
team anyone who is actually a member, but hasn't contributed for... let's
say 2 years? Of course this isn't a permanent thing, and we can simply move
alumni back to the relevant team if they become active again.
2. *We move non-members out of our GitHub organization*, or to "external
collaborators" (that's a GitHub feature) if still necessary.
3. *We schedule yearly audits of our GitHub configuration* to review access
rights again in the future, and move people to the Alumni team as necessary.
Note moving people in and out of teams will get them notified, so I would
send another email directly to impacted people before/during the move, to
avoid this being seen as personal/insulting. It's really not.
*Thoughts, opinions, +1s?*
Yoann Rodière
Hibernate team
3 days, 22 hours
- 6
- 6
- ← Newer
- 1
- Older →