Skip to content

Releases: paypal/squbs

0.15.0 Release

11 Mar 16:59
86d6a7b
Compare
Choose a tag to compare

squbs 0.15.0 is a major upgrade supporting Akka 2.6, Akka HTTP 10.2, and the latest Alpakka ecosystem. With that, support for Scala 2.11 has been dropped.

0.14.0 Release

18 Jan 16:27
Compare
Choose a tag to compare

The squbs 0.14.0 milestone is to support Scala version 2.13 as well as dependency version upgrades.

  • Scala 2.13 support and latest libs (#737)
  • PersistentBufferAtLeastOnce: Don't drop elements if no commits are made (#736)

0.13.0 Release

03 Jan 21:17
Compare
Choose a tag to compare

This squbs 0.13.0 milestone is primarily a bug fix only release. We also have updated the akka and jackson dependency versions.

  • service infra timeout needs to be more configurable #711
  • Upgrade dependency versions to Akka 2.5.27, Akka HTTP 10.1.11, Jackson 2.10.1

0.12.0

14 Mar 19:32
Compare
Choose a tag to compare

This 0.12.0 release is primarily a bug fix release. The key changes in this release are:

  • squbs support for Scala version 2.11 is now available (contributed by @vk9)
  • Standardize the java APIs to use java.time.Duration consistently (contributed by @jiminhsieh)
  • Update the dependency versions, including akka version 2.5.21 and akka-http version 10.1.7
  • Retry stage must log error if entries cannot be removed from retry registry
  • Allow access to PerpetualStream matValue of all types and from both Java and Scala
  • Unicomplex should not eat exception when starting listeners

The full list of all closed issues for the 0.12.0 release milestone are here on GitHub.

Several contributors made this release possible. Thank you.

0.10.0

30 Mar 19:18
Compare
Choose a tag to compare

The key features of 0.10.0 release are:

  • Scala 2.12, Akka 2.5, Akka HTTP 10.1.0
  • Retry Akka Stream Stage now supports exponential back-off delay, please see the doc.
  • Metrics for Retry stage.
  • BoundedOrdering stage, please see the doc. OrderingStage is renamed and max bound feature added.
  • Materialization Metrics Collector Stage can be used to see metrics on how many times a stream is materialized, please see the doc. This stage is already integrated with squbs services, so incoming http connection metrics can be observed.
  • Java API for Perpetual Stream, please see the doc.
  • Java API for Pipeline Flow Factory, please see the doc.
  • Graph Stage for flow demand and supply metrics #464.

The full list of all closed issues for the 0.10.0 release milestone are here on GitHub.

0.9.2

20 Oct 22:21
Compare
Choose a tag to compare

The 0.9.2 release is a hot fix release with these changes:

  • Drain response entity when timeout occurs in TimeoutBidi
  • Http client circuit breaker should allow a drainer
  • Fixed CircuitBreaker spinning and consuming CPU
  • Allow customizing ActorMaterializer settings for server side HTTP request handling
  • Update to Akka version 2.4.20 and Akka HTTP 10.0.10
  • Change squbs activator templates to giter8

The full list of all closed issues for the 0.9.2 release milestone are here on GitHub.

0.9.1

24 Jul 16:40
Compare
Choose a tag to compare

The key feature of 0.9.1 release is:

  • PerpetualStream should allow to override the lifecycle phase to run the stream. This feature allows to connect a PerpetualStream with HTTP flows via MergeHub for end-to-end streaming. Please see the docs here. Also, see the "Override Lifecycle State to run the stream" section in the same doc.

The full list of closed issues can be found at 0.9.1 milestone on GitHub.

0.9.0

15 May 17:53
Compare
Choose a tag to compare

The key faetures of 0.9.0 release are:

  • Move HTTP Client to Akka HTTP and redesign to provide simpler configuration and use of Akka HTTP APIs. Please see the docs here. While still mostly relying on Akka HTTP API, squbs HTTP client adds the following features on top:
    • Service Discovery: Lets any service discovery mechanism to be plugged in and allows resolving HTTP endpoints by string identifiers, e.g., paymentserv.
    • Per Client configuration: Let's each client to individually override defaults in application.conf.
    • Pipeline: Allows a BidiAkka Streams flow to be registered globally or individually for clients.
    • Metrics: Provides Codahale Metrics out-of-the-box for each client.
    • JMX Beans: Exposes the configuration of each client as JMX beans.
    • Circuit Breaker: Provides resiliency with a stream based circuit breaker.
  • Remove all Spray related code and dependencies.
  • Out of the box Codahale metrics for Akka HTTP server and client.
  • Circuit Breaker for Akka Streams with metrics. Please see the docs here.
  • Timeout Flow for Akka Streams. Please see the docs here.
  • Akka Streams based HTTP Request/Response Pipeline for both server and client side. Please see the docs here.
  • Redesigned Resolver chain to support any resource of any type. Please see the docs here.
  • Further improvements on testing, Java API and more.

The full list of closed issues can be found at 0.9.0 milestone on GitHub.