Open GDS 2.24.0 build fails at :licensing: with missing resource neo4j-graphdb-api/2025.11.0

[JohT]

Describe the bug

The build ./gradlew -Dorg.gradle.logging.level=info "-Dorg.gradle.jvmargs=-Xmx2g" -Pneo4jVersion=2025.11.2 -- :open-packaging:shadowCopy of tag 2.24.0 fails with

Resource missing. [HTTP GET: https://repo.maven.apache.org/maven2/org/neo4j/annotations/2025.11.0/annotations-2025.11.0.pom]
Resource missing. [HTTP GET: https://repo.maven.apache.org/maven2/org/neo4j/neo4j-graphdb-api/2025.11.0/neo4j-graphdb-api-2025.11.0.pom]

To Reproduce

GDS version: 2.24.0
Neo4j version: 2025.11.2
Java version: Java 21.0.6+7.0.LTS (Temurin-Hotspot)
Operating system: Ubuntu 24.04.3 LTS

Steps to reproduce the behavior:

• Checkout 2.24.0
• Run ./gradlew -Dorg.gradle.logging.level=info "-Dorg.gradle.jvmargs=-Xmx2g" -Pneo4jVersion=2025.11.2 -- :open-packaging:shadowCopy

Expected behavior
Successful build with newer (but unofficial) reference 71.68.83-v44-310b5f1b7f. See workaround JohT/open-graph-data-science-packaging#96

Additional context

• Gradle build log (part):

> Task :licensing:compileJava FAILED
Resource missing. [HTTP GET: https://repo.maven.apache.org/maven2/org/neo4j/annotations/2025.11.0/annotations-2025.11.0.pom]
Resource missing. [HTTP GET: https://repo.maven.apache.org/maven2/org/neo4j/neo4j-graphdb-api/2025.11.0/neo4j-graphdb-api-2025.11.0.pom]


[Incubating] Problems report is available at: file:///home/runner/work/open-graph-data-science-packaging/open-graph-data-science-packaging/build/reports/problems/problems-report.html
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':licensing:compileJava'.
> Could not resolve all files for configuration ':licensing:compileClasspath'.
   > Could not find org.neo4j:annotations:2025.11.0.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/neo4j/annotations/2025.11.0/annotations-2025.11.0.pom
       - file:/home/runner/work/open-graph-data-science-packaging/open-graph-data-science-packaging/neo4j-repo/org/neo4j/annotations/2025.11.0/annotations-2025.11.0.pom
     Required by:
         project ':licensing'
   > Could not find org.neo4j:neo4j-graphdb-api:2025.11.0.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/neo4j/neo4j-graphdb-api/2025.11.0/neo4j-graphdb-api-2025.11.0.pom
       - file:/home/runner/work/open-graph-data-science-packaging/open-graph-data-science-packaging/neo4j-repo/org/neo4j/neo4j-graphdb-api/2025.11.0/neo4j-graphdb-api-2025.11.0.pom
     Required by:
         project ':licensing'

[IoannisPanagiotas]

Hi @JohT.

i am so sorry you have had problems twice in a row now.

This is due to a maven dependency mistake where dependencies were set to look for 11.0, but the database ended up being published with version 11.2 instead.

I think we are going to look into making our process a little more resilient, because from our side we deliver something that works for version xxxx.xx.0, but in extreme cases such as this month's release this contract might be broken.
Thankfully you have found a walkaround. The alternative solution would be as @vnickolov highlighted last month to update the dependencies to the correct version. I have put a note in the release notes to help others.

Best regards and sorry for all the trouble.
Ioannis.

[JohT]

Hi @IoannisPanagiotas,

thanks. I'll most likely overcome this with my workaround.

🎅 Approaching holidays and with the vibe of wishes in the air 😁:

Is there a chance to add a pipeline that runs the open build documented in Building the library in the section "Packaging the library"?

I'm open for volunteering for that including creating a new feature request issue if you like. There already exists something similar with #275, but that is - I guess - more effort than just running the build as an additional check.

[IoannisPanagiotas]

Hi again @JohT ,

Hopefully from next release, we are going to be more resilisent with this, tried some things ealier today that should prevent such mishaps 🤞.

I will bring your suggestion into the attention of the rest of the team, but almost everyone in the team is off for holidays and it might take few days before we discuss that as they unfortunately do not yet allow me to take all the decisions by myself :)

I will try to post an update when there are news. As far as i can tell your repository is already doing something among these lines, right?

Thank you very much for your interest in our work and best of wishes for the holidays and the end of the year!

[JohT]

As far as i can tell your repository is already doing something among these lines, right?

Yes.

In terms of fail-fast you would get earlier feedback with an integrated pipeline. Leaving it as is means that my pipeline might fail after your release and I'm reporting it to you (for now manually) with an issue. Since it doesn't happen that often, I'm also fine with that.

I wish you all also nice holidays and a good start into the new year 🎆.

[IoannisPanagiotas]

Hi again @JohT,

Heads up, you might notice the :package is failing again, you should use neo4jVersion to 2026.01.4 (when it is released) the way you've done in the best or by changing the toml file.
We had to roll back our fix (which we applied for 2.25 and hopefully you avoided manual fixing).

As for your other question, no action yet, but we will see :)

Best,
Ioannis.