Repository navigation
chore(renovate): disable hibernate updates to block replacement PRs - #153
Merged
Merged
Conversation
Renovate's config:base replacement rules propose replacing org.hibernate:hibernate-core with org.hibernate.orm:hibernate-core 7.x, which fails to compile (Hibernate 7 removed the org.hibernate.criterion API this portlet uses and requires Java 17+). The existing allowedVersions: "< 4.0" constraint does not gate replacement update-types, so those PRs slipped through. Disable hibernate updates entirely so both version bumps and replacement PRs are suppressed. Hibernate 3.6.10 is EOL and frozen here until a coordinated Spring 5+/Jakarta/Java 17 migration.
bjagg
approved these changes
Sep 21, 2026
bjagg
left a comment
Member
There was a problem hiding this comment.
Approving.
Verified before merging:
renovate.jsonparses cleanly (5 packageRules).- Same empirical confirmation as AnnouncementsPortlet #373 — the replacement PR was created despite the
allowedVersionscap. - Nothing lost by disabling: this portlet is on the Hibernate 3.6.x line, long past EOL, so there are no in-line updates to surface.
One note: the org.hibernate: prefix also catches hibernate-validator, pinned here at 4.2.0.Final (2011). That was already effectively frozen — 4.2.0 sits above the old < 4.0 cap, so Renovate had nothing it could propose — so this change doesn't alter its status. Worth knowing that the validator is silently in scope of a rule whose description only mentions ORM, if anyone later wonders why it never gets update PRs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Renovate's
config:basebuilt-in replacement rules propose replacingorg.hibernate:hibernate-corewithorg.hibernate.orm:hibernate-core7.x(see #151). That change cannot build here:org.hibernate.criterionCriteria API this portlet's DAOs are built on (removed back in Hibernate 5.2).The existing
allowedVersions: "< 4.0"rule constrains version updates but does not gatereplacementupdate-types, so the replacement PR slipped through.Change
Set the existing
org.hibernate:/org.hibernate.orm:packageRule toenabled: false. Disabling the package short-circuits all update-types, so both version bumps and replacement PRs are suppressed.Hibernate 3.6.10.Final is EOL and effectively frozen for this portlet until a coordinated Spring 5+ / Jakarta EE / Java 17 migration, so there is no practical loss from disabling updates entirely.
Notes