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

[dependabot]

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

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 is a Dependabot-generated dependency bump for org.eclipse.rdf4j:rdf4j-rio-datatypes from 4.3.9 to 5.2.2 in klab.services.reasoner/pom.xml. The change is a major-version upgrade (4.x → 5.x), not just a patch bump.

Key concern: The two sibling rdf4j modules in the same pom.xml — rdf4j-rio-turtle (4.3.7) and rdf4j-rio-languages (4.3.9) — are left behind at 4.x. These three artifacts are co-released as part of the same rdf4j-rio parent module and are designed to run at the same version. Promoting only one to 5.x creates a mixed-version classpath that rdf4j does not test or support.

• While binary inspection found no immediate classpath explosion for the current usage pattern, the misalignment contradicts rdf4j's own release model and is fragile.
• The fix is straightforward: either bump all three rdf4j sibling dependencies to 5.2.2, or revert rdf4j-rio-datatypes to align with the others."

Confidence Score: 3/5

Not safe to merge as-is: only one of three tightly-coupled rdf4j-rio sibling modules was bumped to 5.x, leaving the others on 4.x in a configuration that rdf4j never tests.

Major-version bump of a single module within a co-released module family, leaving siblings at a different major version, is a known pattern for subtle runtime failures. The incompleteness of the upgrade is the primary blocker.

klab.services.reasoner/pom.xml — the three rdf4j-rio sibling versions must be aligned.

Important Files Changed

Filename	Overview
klab.services.reasoner/pom.xml	Bumps rdf4j-rio-datatypes to 5.2.2 (major version), but leaves sibling rdf4j-rio-turtle (4.3.7) and rdf4j-rio-languages (4.3.9) on 4.x, creating a cross-major-version mismatch within the same co-released artifact family.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[klab.services.reasoner] --> B[rdf4j-rio-turtle v4.3.7]
    A --> C[rdf4j-rio-datatypes v5.2.2]
    A --> D[rdf4j-rio-languages v4.3.9]
    B -. runtime dep .-> E[rdf4j-rio-datatypes v4.3.7\n expected by turtle]
    B -. runtime dep .-> F[rdf4j-rio-languages v4.3.7\n expected by turtle]
    C -.->|version conflict| E
    style C fill:#f66,color:#fff
    style E fill:#f96
    style F fill:#f96

Loading

Comments Outside Diff (1)

1. klab.services.reasoner/pom.xml, line 49-55 (link)

   rdf4j sibling modules out of sync after major-version bump

   This PR bumps rdf4j-rio-datatypes to 5.2.2 (a major-version jump from 4.3.9), but the two sibling rdf4j modules declared immediately adjacent remain on 4.x:

   • rdf4j-rio-turtle: 4.3.7 (line 44)
   • rdf4j-rio-languages: 4.3.9 (line 54)

   All three artifacts are sub-modules of the same rdf4j-rio parent POM and are released and tested together at the same version. rdf4j-rio-turtle itself internally declares a runtime dependency on both rdf4j-rio-datatypes and rdf4j-rio-languages at the matching version, so mixing a 5.x artifact with 4.x counterparts is contrary to how the library is designed and tested.

   While Maven's nearest-wins resolution may prevent an immediate classpath crash, this misalignment relies on implementation details that could silently break in a future 5.x patch release. All three sibling dependencies should be aligned to the same version (ideally all bumped to 5.2.2, or rdf4j-rio-datatypes reverted to stay in line with the others).

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

[dependabot]

Superseded by #74.