After an exciting journey, we are pleased to announce the General Availability release of the Spring Cloud Stream Fishtown release train - Fishtown.RELEASE/2.1.0.RELEASE.

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-stream-dependencies</artifactId>
            <version>Fishtown.RELEASE</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

Spring Cloud Stream Fishtown (2.1.0.RELEASE) is available for use in Maven Central and the Spring Repo.

This release encompasses the following:

Notable Dependency Upgrades

• Spring Boot 2.1.x
• Reactor Californium.RELEASE
• Spring Cloud Function 2.0.0.RELEASE

Core

• Support for Spring Cloud Function programming model (see M2 release announcement for more details)
• Support for Message Listener container customization by simply registering implementation of ListenerContainerCustomizer bean.
• Binding properties precedence support (see M1 release announcement for more details)
• Support for output binding actuator endpoints was added as well.

Rabbit Binder

• Exposed support for setting queue length as and overflow policy
• Multiplex support
• Support for Consumer Tags

Kafka Binder

• Wild cards are now supported in kafka topic names in the binder [kafka binder]
• New annotation KafkaStreamsStateStore for creating state stores in lower level processor API in kafka streams [kafka streams binder]
• Removing the creation of unnecessary repartition topics in the kafka streams binder
• Consuming from multiple topics in kafka streams binder
• Improvements in in interactive query support in kafka streams binder - Multiple consumers and querying across them are now supported.
• QueryableStoreRegistry is deprecated and a new API is provided called InteractiveQueryService. In addition to provide ability to query state stores, this API also gives information about the host where the consumer is running.
• Multiplex support

Once again huge thanks to all the community contributors!!!

As always, we welcome feedback and contributions, so please reach out to us on Stackoverflow or GitHub or via Gitter.