Release spring-batch-neo4j version 1.0.0

[scordio]

I prepared a draft for the release notes.

[meistermeier]

Thinking about this, we should discuss if we want to pull the version to SDN latest (7.3.5) before release.
Don't know the interop with Spring Boot but it seems to make sense, or?

[scordio]

Indeed, @meistermeier – I wasn't thinking about checking if the SDN version was the latest available.

To guarantee interoperability, I let Spring Boot drive all the dependency versions in the Notion module:

spring-batch-extensions/spring-batch-notion/pom.xml

Lines 5 to 10 in 0b9b9ad

	<parent>
	<groupId>org.springframework.boot</groupId>
	<artifactId>spring-boot-starter-parent</artifactId>
	<version>3.3.5</version>
	<relativePath/>
	</parent>

We may not want to refactor the Neo4j POM right now, but I agree we should bring SDN to the latest.

Is it a simple version increase, or is there more to consider when upgrading from 7.2 to 7.3?

[scordio]

Raised #158.

[meistermeier]

Yes, 7.3 can be used as a drop-in replacement for 7.2. No changes required.

[scordio]

We might want to wait for #159 before releasing.

[scordio]

@fmbenhassine I think we are ready to release the Neo4j module 🙂

[fmbenhassine]

I acknowledge this request to release the neo4j module. I am just waiting for an update from our Infra team to be able to proceed with the release to Maven Central. I will update this ticket once the release is done. Thank you for your comprehension.

[scordio]

Hi @fmbenhassine, I just wanted to highlight that OSSRH will reach end-of-life on June 30th, in case this will impact the release process of the Spring Batch extensions.