[yagee-de]

Minor/patch updates: AWS SDK 2.55.5, Jackson 2.22.3, JUnit 6.1.3, Log4j 2.26.1, Mockito 5.24.0, Guava 33.7.1, Bouncy Castle 1.86, H2 2.5.250, iText 9.7.1, PDFBox 3.0.8, Selenium 4.49.0, Swagger 2.2.55, Neo4j driver 6.3.0, Netty 4.1.138 and others.

Major updates: Saxon-HE 13.0, rdf4j 6.1.0, hk2 4.0.2, ICU4J 78.3, Rhino 1.9.1, vis-network 10.0.3, Hibernate ORM 7.4.10.

Required adjustments:

• Guava: use Duration overloads of refreshAfterWrite/expireAfterWrite
• Bouncy Castle: use BCrypt.generate(..., false), password is already null-terminated
• ICU4J: drop now redundant Calendar casts after clone(); Meiji era starts on 23.10.1868 (CLDR 48)
• Saxon: vendor URL is now https://www.saxonica.com/

mets-model stays at 2.0: 2.1 fails on METS documents without metsHdr.

Link to jira.

Pull Request Checklist (Author)

Please go through the following checklist before assigning the PR for review:

Ticket & Documentation

• The issue in the ticket is clearly described and the solution is documented.
• Design decisions (if any) are explained.
• The ticket references the correct source and target branches.
• The fixed-version is correctly set in the ticket and matches the PR's target branch (main).

Feature & Improvement Specific Checks

• Instructions on how to test or use the feature are included or linked (e.g. to documentation).
• For UI changes: before & after screenshots are attached.
• New features or migrations are documented.
• Does this change affect existing applications, data, or configurations?
  • Yes: Is a migration required? If yes, describe it.
  • Breaking change is marked in the commit message.

Bugfix-Specific Checks

• Affected version is listed in the ticket.
• Minimal code changes were made (no refactoring).
• This PR truly fixes only the reported bug.
• No breaking changes are introduced.
• A relevant test was added (if feasible).

Testing

• I have tested the changes locally.
• The feature behaves as described in the ticket.
• Were existing tests modified?
  • Yes: explain the changes for reviewers.

MCR Conventions & Metadata

• MCR naming conventions are followed
• If the public API has changed:
  • Old API is deprecated or a migration is documented.
  • If not, no action needed.
• Java license headers are added where necessary.
• Javadoc is written for non-self-explanatory classes/methods (Clean Code).
• All configuration options are documented in Javadoc and mycore.properties.
• No default properties are hardcoded — all set via mycore.properties.

Multi-Repo Considerations

• Is an equivalent PR in MIR required?
  • If yes, is it already created?