Bump org.eclipse.rdf4j:rdf4j-rio-datatypes from 4.3.9 to 5.3.1

[dependabot]

Bumps org.eclipse.rdf4j:rdf4j-rio-datatypes from 4.3.9 to 5.3.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[greptile-apps]

Greptile Summary

This PR bumps org.eclipse.rdf4j:rdf4j-rio-datatypes from 4.3.9 to 5.3.1 in the reasoner module's pom.xml. The change creates a major-version split within the three co-located RDF4J Rio dependencies — rdf4j-rio-turtle (4.3.7) and rdf4j-rio-languages (4.3.9) are left behind on 4.x while datatypes moves to 5.x.

• Version mismatch (P1): All three rdf4j-rio-* modules belong to the same RDF4J Rio framework and are designed to be used at a consistent version. Bumping only rdf4j-rio-datatypes to a new major version while the other two stay on 4.x risks runtime class-incompatibility errors; the remaining 4.x modules transitively expect a 4.x datatypes API, which this explicit override replaces with a potentially breaking 5.x version.

Confidence Score: 3/5

Not safe to merge as-is — the major-version mismatch between rdf4j-rio-datatypes (5.x) and the other two RDF4J Rio modules (4.x) risks runtime incompatibility.

A single P1 finding (version mismatch that can cause runtime class-incompatibility) lowers confidence below 4. The fix is straightforward (align all three RDF4J modules to the same version), but the current state is potentially broken.

klab.services.reasoner/pom.xml — needs all three rdf4j-rio-* versions aligned before merging.

Important Files Changed

Filename	Overview
klab.services.reasoner/pom.xml	Bumps rdf4j-rio-datatypes from 4.3.9 to 5.3.1, creating a major-version mismatch with sibling RDF4J dependencies (rdf4j-rio-turtle 4.3.7, rdf4j-rio-languages 4.3.9) that remain on 4.x.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[klab.services.reasoner] --> B[rdf4j-rio-turtle 4.3.7]
    A --> C[rdf4j-rio-datatypes 5.3.1 ⚠️ bumped]
    A --> D[rdf4j-rio-languages 4.3.9]
    B -->|transitive dep| E[rdf4j-rio-datatypes 4.x]
    D -->|transitive dep| E
    E -.->|overridden by explicit declaration| C
    style C fill:#f99,stroke:#c00
    style E fill:#ffd,stroke:#999

Loading

_{Reviews (1): Last reviewed commit: "Bump org.eclipse.rdf4j:rdf4j-rio-datatyp..." | Re-trigger Greptile}

[greptile-apps]

RDF4J version mismatch across sibling modules

rdf4j-rio-datatypes is now on 5.3.1 while rdf4j-rio-turtle (line 44) stays on 4.3.7 and rdf4j-rio-languages (line 54) stays on 4.3.9. All three artifacts are part of the same RDF4J Rio framework and are designed to ship and run together at the same version. rdf4j-rio-turtle and rdf4j-rio-languages declare a transitive dependency on rdf4j-rio-datatypes at a 4.x version; the explicit 5.3.1 declaration here overrides that transitive pin, potentially exposing the 4.x modules to a rdf4j-rio-datatypes API that changed across the major version boundary. Either all three should be bumped to 5.3.1, or this bump should be reverted until the full suite can be aligned.