Skip to content

Releases: spring-cloud/spring-cloud-bindings

v2.0.4 Release

12 Nov 19:56
Compare
Choose a tag to compare

This release integrates 1 bug fix:

Start using it now!

		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-bindings</artifactId>
			<version>2.0.4</version>
		</dependency>

v2.0.3 Release

22 Mar 18:40
Compare
Choose a tag to compare

This release integrates 2 bug fixes:

Start using it now!

		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-bindings</artifactId>
			<version>2.0.3</version>
		</dependency>

Spring Cloud Bindings 2.0.2: Bug fix release

15 Aug 17:43
Compare
Choose a tag to compare

This release just integrates a bug fix (SCB was not properly closing the directories from which it was reading the binding files) and some refactoring; in fact all that happened in this PR: #105

Start using it now!

		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-bindings</artifactId>
			<version>2.0.2</version>
		</dependency>

Thanks to @violetagg , for raising the issue and helping with the fix.

Spring Cloud Bindings 2.0.1: Spring Boot 3 support

22 Jul 00:30
Compare
Choose a tag to compare

After several failed attempts, a lot of discussion and help from the community, finally, here is it, the first Spring Cloud Bindings release compatible with Spring Boot 3 support.

Said differently, Spring Cloud Bindings 2 now translate Kubernetes Service Binding Specification into proper Spring Boot 3 application configuration properties

It also includes default activation now; you no longer need to to provide the JAVA_TOOL_OPTIONS=-Dorg.springframework.cloud.bindings.boot.enable=true; just drop the jar in your classpath, and Spring will autocofigure to connect to your services!

Start using it now!

		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-bindings</artifactId>
			<version>2.0.1</version>
		</dependency>

Thanks to @abelsromero , @Kehrlann @pivotal-david-osullivan , @scottfrederick and all the others who participated in the discussions and testing!