Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency com.lightbend.lagom:lagom-javadsl-testkit_2.11 to v1.5.5 - abandoned #599

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mend-for-jackfan.us.kg[bot]
Copy link

This PR contains the following updates:

Package Update Change
com.lightbend.lagom:lagom-javadsl-testkit_2.11 (source) minor 1.4.0 -> 1.5.5

By merging this PR, the below issues will be automatically resolved and closed:

Severity CVSS Score CVE GitHub Issue
High 10.0 CVE-2018-14721 #22
High 9.8 CVE-2018-11307 #193
High 9.8 CVE-2018-14718 #69
High 9.8 CVE-2018-14719 #68
High 9.8 CVE-2018-14720 #20
High 9.8 CVE-2018-19360 #207
High 9.8 CVE-2018-19361 #205
High 9.8 CVE-2018-19362 #204
High 9.8 CVE-2019-14379 #60
High 9.8 CVE-2019-14540 #297
High 9.8 CVE-2019-14892 #343
High 9.8 CVE-2019-14893 #341
High 9.8 CVE-2019-16335 #25
High 9.8 CVE-2019-16942 #331
High 9.8 CVE-2019-16943 #333
High 9.8 CVE-2019-17267 #146
High 9.8 CVE-2019-20330 #219
High 9.8 CVE-2020-8840 #53
High 9.8 CVE-2020-9546 #345
High 9.8 CVE-2020-9548 #347
High 8.1 CVE-2018-5968 #46
High 8.1 CVE-2020-14060 #56
High 8.1 CVE-2020-14061 #57
High 8.1 CVE-2020-14062 #58
High 8.1 CVE-2020-14195 #73
High 8.1 CVE-2020-24616 #209
High 8.1 CVE-2020-24750 #213
High 8.1 CVE-2020-35490 #326
High 8.1 CVE-2020-35491 #329
High 8.1 CVE-2020-35728 #188
High 7.5 CVE-2018-12022 #308
High 7.5 CVE-2018-12023 #309
High 7.5 CVE-2019-12086 #3
High 7.5 CVE-2019-14439 #317
High 7.5 CVE-2019-16869 #385
Medium 5.9 CVE-2019-12384 #378
Medium 5.9 CVE-2019-12814 #151

Release Notes

lagom/lagom

v1.5.5

Compare Source

We are pleased to announce the release of Lagom Framework 1.5.5. This is the latest stable release of Play 1.5.x series.

Changelog

This release mainly includes security and overall fixes.

For more details see the full list of changes.

Credits

Thanks to the community for their detailed bug reports and contributions. Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Dale Wijnand, Ignasi Marimon-Clos, Tim Moore, Sergey Morgunov, Stephan Emmerich, Enno Runne, Marcos Pereira.

Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.

v1.5.4

Compare Source

The Lagom team has released the versions 1.5.4. For a list of the specific changes in Lagom 1.5.4, see the change log.

Highlights

  • #​2240 Override default discovery method
  • #​2280 Default to only 1 max inflight request per connection

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release: Ignasi Marimon-Clos, Tim Moore, Matthias Kurz, Renato Cavalcanti.

v1.5.3

Compare Source

The Lagom team has released the versions 1.5.3 (due to an error during the release we had to skip 1.5.2). For a list of the specific changes in Lagom 1.5.3, see the change log.

Highlights

  • #​2191 Bump Akka to 2.5.25, which backports some of Akka 2.6's serializers, allowing rolling upgrades between Akka 2.5 and Akka 2.6, and, thus, between Lagom 1.5 and Lagom 1.6.
  • #​2174 Fix cross-building (++/+) Lagom apps
  • #​2165 Update to Scala 2.12.9
  • #​1979 Fix akka.discovery.method in dev-mode
  • #​1960 Setup default discovery methods
  • #​1948 Fix the Akka Discovery ServiceLocator module ids for Java and Scala DSLs
  • #​1950 Use Maven's built-in check of version for Lagom-Maven-Plugin
  • #​1924 Add protobuf akka serializers

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Dale Wijnand, Ignasi Marimon-Clos, Marcos Pereira, Sergey Morgunov, Tim Moore, fgonzalez, Dmitriy Grigoryev.

v1.5.1

Compare Source

These releases bring into Lagom a new Service Locator implementation, based on Akka's Service Discovery. This component was previously released as an apart library, lagom-akka-discovery-service-locator, and intended to be a replacement for the Service Locator previously offered by Lightbend Orchestration.

For more information, consult the corresponding documentation for Akka Discovery integration:

For a list of the specific changes in Lagom 1.5.1, see the change log (1.5.1).

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Steve Swing, Ignasi Marimon-Clos, Dale Wijnand, Tim Moore, Alden Torres.

v1.5.0

Compare Source

We are happy to announce the availability of Lagom 1.5.0. This is the GA release of Lagom 1.5.0 and is production ready. We invite all our users to upgrade.

This version builds on top of the 2.7.x series of Play, Alpakka Kafka 1.0, and the latest improvements on Akka and Akka Management. See GitHub for the full list of commits.

Here’s a list of the most relevant improvements.

Akka Management

Akka Management is a suite of tools for operating Akka powered applications. Akka Management uses a dedicated HTTP port to expose a few routes allowing remote inspection of the state of the Akka Actor System. For example, if the process is a member of an Akka Cluster, these endpoints will report if the node already joined the cluster.

Lagom exposes the Akka Management HTTP port out of the box. Lagom will add Health Check routes by default. You can reuse library provided health checks or plugin your own. For example, Lagom uses cluster status to determine when the node is healthy. This is called Cluster Membership Check and is provided by the Akka Cluster HTTP Management library.

Another improvement Lagom 1.5 introduces, thanks to the adoption of Akka Management, is the simpler, more robust cluster formation via Akka Cluster Bootstrap. Instead of using a static list of seed nodes or relying on convoluted custom scripts to build the list of seed nodes dynamically, Cluster Bootstrap discovers the existing nodes via plugins adapting Akka Cluster Bootstrap to your orchestration environment (e.g. Kubernetes, Marathon). A static list of seed nodes is still supported but we recommend migrating to Cluster Bootstrap.

Deployment with Kubernetes or Red Hat OpenShift

Lagom 1.5.0 will no longer support Lightbend Orchestration (which was Incubating). Despite accelerating the first deployment, using Lightbend Orchestration was producing friction and reducing flexibility to tune the deployment. Moving forward, there will be no automated handling of the deployment and the suggested way is to manually maintain the production settings, the deployment descriptors and related scripts.

If you are targeting OpenShift or Kubernetes environments the new Guide to Deploy Lightbend Applications covers all the steps and details (including a sample application) to set up and tune your system.

Akka gRPC integration

Lagom 1.5.0 introduces incubating support for Akka gRPC for cross-service communication. The original HTTP/JSON-based transport is not disappearing but, instead, Lagom introduces gRPC so users can choose to expose alternative transports increasing the adoption of their services.

This feature drove some smaller improvements which non-gRPC users will also welcome.
Lagom already supported HTTP/2 since it is built on top of Play. In Lagom 1.5 we’ve reviewed all the necessary pieces so HTTP/2 can also be used on dev mode. In the same spirit, it is now also possible to use encrypted (TLS) communication on dev mode.

As a final improvement driven by the adoption of gRPC, Lagom 1.5 now supports Additional Routers (Java API / Scala API), which lets you embed any vanilla Play Router into a Lagom service. You are now able to easily reuse the Play and Akka building blocks whenever the Lagom API is not enough to complete the task at hand. Using Additional Routers it is trivial to reuse Play code you already had or extend Lagom with low-level features supported in Play but not exposed in Lagom directly (such as uploading files).

Couchbase Persistence Support

Lagom 1.5 also offers optional support for Couchbase as a new database option for persistent entities and read side processors through the Akka Persistence Couchbase module. Currently available in an Incubating early access release, Akka Persistence Couchbase has been built to work with Lagom 1.5 and the 1.0 release is coming soon. See the documentation for Couchbase Persistent Entities and Couchbase Read-Side support for more details.

Migrating from previous versions

This release introduces very little changes over the 1.5.0-RC2 so if you already moved to that version the upgrade should be trivial. If you are still using Lagom 1.4.x we recommend you first migrate to the latest version available of Lagom 1.4 series and then migrate to Lagom 1.5. If you are using a version older than 1.4.x, you should migrate one version at a time. For example: from 1.3.9 to 1.3.11 (because 1.3.11 is 1.3.latest), then from 1.3.11 to 1.4.latest and finally to 1.5.x. Read the appropriate release notes and migration guides (Java / Scala) on each step.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

commits author    
     53 Ignasi Marimon-Clos
     37 Renato Cavalcanti
     20 Tim Moore
     16 Dale Wijnand
     15 Elijah Rippeth
     11 Marcos Pereira
      4 Martynas Mickevičius
      3 Ayush Prashar
      2 Alden Torres
      1 sullis
      1 danielklein45
      1 Zhonglai Zhang
      1 Sergey Morgunov
      1 Riccardo Sirigu
      1 Prashant Sharma
      1 Piyush Goyal
      1 Kunal sethi
      1 João Guitana
      1 Ido Shamun
      1 Enno
      1 Corey Auger
      1 Brent Eritou
      1 0xflotus

v1.4.15

Compare Source

The Play Team is pleased to announce the release of Lagom Framework 1.4.15. This is the latest stable release of Lagom 1.4.x series.

Lagom 1.4.15 includes a backport of https://github.com/lagom/lagom/pull/2161 to fix a problem that appears when running tasks across multiple Scala versions, for example, sbt +publishLocal. There are also minor internal changes and documentation fixes. For a list of the specific changes in Lagom 1.4.15 see the change log (1.4.15).

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Play core team’s efforts. Lightbend offers commercial support for Lagom.

v1.4.14

Compare Source

The Play Team is pleased to announce the release of Lagom Framework 1.4.14. This is the latest stable release of Lagom 1.4.x series.

Lagom 1.4.14 includes a backport of https://github.com/lagom/lagom/pull/1773. Special thanks to @​ihostage for the fix.

For a list of the specific changes in Lagom 1.4.14 see the change log (1.4.14).

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Play core team’s efforts. Lightbend offers commercial support for Lagom.

v1.4.13

Compare Source

The Play Team is pleased to announce the release of Lagom Framework 1.4.13. This is the latest stable release of Lagom 1.4.x series.

Lagom 1.4.13 brings in Play 2.6.23 and a new version of play-ws (v1.1.13) that includes an important bug fix on streamed calls. In case of an error, after a connection is established, the error is now properly propagated. See playframework/play-ws#​340

For a list of the specific changes in Lagom 1.4.13 see the change log (1.4.13).

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Play core team’s efforts. Lightbend offers commercial support for Lagom.

v1.4.12

Compare Source

These releases bring into Lagom a new Service Locator implementation, based on Akka's Service Discovery. This component was previously released as an apart library, lagom-akka-discovery-service-locator, and intended to be a replacement for the Service Locator previously offered by Lightbend Orchestration.

In order to allow a smoother transition for Lagom 1.4 users, we decided to include it in 1.4.12. So users can choose to first migrate their Lagom 1.4 application to Akka Service Discovery and then to Lagom 1.5. Of course, this is not a required step. It is also possible to migrate directly from Lagom 1.4 and Lightbend Orchestration to Lagom 1.5 and Akka Service Discovery.

For more information, consult the corresponding documentation for Akka Discovery integration:

For a list of the specific changes in Lagom 1.4.12 see the change log (1.4.12).

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release: Renato Cavalcanti, Steve Swing, Ignasi Marimon-Clos, Dale Wijnand, Tim Moore, Alden Torres.

v1.4.11

Compare Source

The Lagom team has released Lagom 1.4.11.

This release upgrades Akka to resolve a compatibility problem with Lightbend Orchestration 1.7.3.

Highlights

  • Updates Akka to version 2.5.20 which stabilizes some APIs and brings bug fixes.

If you are a user of Lightbend Orchestration you will have to upgrade your dependency of the sbt-reactive-app plugin to 1.7.3.

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.11 milestone.

Updating a Lagom project to version 1.4.11

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

commits  added  removed  author
1            4        2  Renato Cavalcanti
1           23       10  Ignasi Marimon-Clos
1            1        1  Marcos Pereira
1            3        3  Tim Moore
1           26        7  Dale Wijnand

v1.4.10

Compare Source

The Lagom team has released Lagom 1.4.10.

This release upgrades Play (and transitively upgrades Akka and Akka HTTP) and Scala.

Highlights

  • Updates Play to 2.6.21 with some minor improvements. This upgrade transitively upgrades Akka and Akka HTTP. Make sure you review Play's announcement for details.

If you are a user of Lightbend Orchestration you will have to upgrade your dependency of the sbt-reactive-app plugin to 1.6.1.

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.10 milestone.

Updating a Lagom project to version 1.4.10

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

commits  added  removed  author    
      2     673     661  Ignasi Marimon-Clos
      1      28      28  Dale Wijnand
      1       2       2  Fran Bermejo

v1.4.9

Compare Source

This release provides a few bug fixes and an improvement.

Highlights

  • Updates Akka to 2.5.18. This Akka release introduces few improvements on the DNS implementation. It also improves the cluster membership handling so if you are using Akka's Split Brain Resolver you may want to upgrade.
  • Updates Akka HTTP to 10.0.14 with an important security fix. It's is unlikely that as a Lagom user you were exposed to the vulnerability, though.
  • Updates Play to 2.6.20 with some minor improvements.
  • Fixes a regression on LagomClientFactory introduced on the 1.4.x series which was causing a LagomClientFactory running inside a Lagom service to interfere with the service in some scenarios causing failures at boot time.

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.9 milestone.

Updating a Lagom project to version 1.4.9

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

commits  added  removed  author    
    4       4      10    Dale Wijnand
    3      82      48    Ignasi Marimon-Clos
    2       2       2    Martijn Riemers
    1       1       1    Ravi Thinakkal
    1     506      76    Renato Cavalcanti

v1.4.8

Compare Source

The Lagom team has released Lagom 1.4.8.

This release provides a bug fix and an improvement.

Highlights

  • Updates Akka to 2.5.16. This Akka release introduces a security fix for a vulnerability affecting users of Akka Cluster with TLS enabled and use a particular random-number-generator. See the Akka announcement for more details.
  • Allow missing application.conf for service clients (PR 1442 contributed by Elijah Rippeth)
  • ... and many documentation improvements.

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.8 milestone.

Updating a Lagom project to version 1.4.8

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

commits  added  removed  author    
    3      15      11    Ignasi Marimon-Clos
    3      19      22    Renato Cavalcanti
    2      12      11    Marcos Pereira
    2       2       2    kunals201
    1       1       1    Jo Vanthournout
    1      36      64    Tim Moore
    1       2       2    Himani Arora
    1      14       2    Elijah Rippeth

v1.4.7

Compare Source

This release provides several bug fixes and updates.

Highlights

  • Updates Akka to 2.5.14
  • Updates Play to 2.6.17 (see also Play 2.6.16 release notes). Play 2.6.17 supports starting the application even when the used RDBMS is not available, but the default configuration is to fail fast. In Lagom, this configuration was overridden to not fail fast.
  • Read side actor restart means that the read side now recovers after a failure in globalPrepare, making it more resilient.
  • Many documentation improvements, especially to remove deprecated APIs in our code examples.

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.7 milestone.

Updating a Lagom project to version 1.4.7

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team’s efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

commits  added  removed  author
12       121    197      Tim Moore
 6       195     86      Marcos Pereira
 2         4      4      adelababinciuc
 1       173     38      Renato Cavalcanti
 1        19     14      Ignasi Marimon-Clos
 1       168      8      Jason Pickens
 1         2      1      Fabrice Sznajderman
 1         5      1      anmolmehta93
 1        34     13      Elijah Rippeth

v1.4.6

Compare Source

This release provides several bug fixes and updates.

Highlights:

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.6 milestone.

Updating a Lagom project to version 1.4.6

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

  commits  added  removed
      7     158     652 Tim Moore
      3      82      52 Ignasi Marimon-Clos
      1      22      14 Patrik Nordwall
      1     100      10 James Roper
      1      21       6 Renato Cavalcanti
      1       2       2 Wade Waldron
      1       2       2 Markus Hennerbichler

v1.4.5

Compare Source

This release provides several bug fixes and updates.

Highlights:

  • Updates Play to 2.6.13
  • Updates Akka to 2.5.12
  • Updates Akka HTTP to 10.0.13
  • Fixes a bug in the TestKit for services using RDBMS persistence that overrides the database driver selected in application.conf with H2 (#​1297)
  • Fixes a bug in the RDBMS persistence module that could cause perpetual timeout errors if creating the offset table fails on startup (#​1336)

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.5 milestone.

Updating a Lagom project to version 1.4.5

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Updating to sbt 1.x

Support for sbt 1.x was quietly released with Lagom 1.4.0, but at the time we had not yet thoroughly tested it with Lagom, so we did not yet document this support or recommend it for most users.

Some adventurous users have been using it since then, and in the meantime we have updated all of our example applications and new project templates. Since we haven't encountered any new problems with sbt 1.x, we now recommend it for all users of Lagom with sbt.

You can update the sbt version in the project/build.properties file. The most recent version at the time of this writing is 1.1.5.

You might also need to update other plugins, global configuration, or custom build configuration. See the sbt documentation for details on migrating from version 0.13.x.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

    8     342      81 Ignasi Marimon-Clos
    4     150      58 Tim Moore
    4       4       4 Play Team
    3       6       6 Brent Eritou
    2      57      40 Sebastien Coquelin
    1       1       3 Renato  Cavalcanti
    1      15      20 Jules Ivanic
    1       1       1 Riccardo Sirigu
    1      91      88 Patrick Prémont
    1      55       1 Kyle Florence
    1       8       6 Ido Shamun
    1      22       3 James Roper

v1.4.4

Compare Source

This release provides a fix for #​1250.

#​1250 only affects Lagom projects making usage of JDBC persistence layer, being it for the journal and/or for read-side tables.

Dependencies upgrades

  • Slick 3.2.1 -> 3.2.3
  • akka-persistence-jdbc 3.1.0 -> 3.3.0

Slick 3.2.3 special note

Since Slick 3.2.2, the maxConnections must equal numThreads. This is to prevent some situations where a deadlock could occur. A warning will be emitted in case maxConnections > numThreads and a runtime exception will be thrown if maxConnections < numThreads. Therefore the best possible configuration is maxConnections == numThreads. See https://github.com/slick/slick/pull/1855 for detailed information.

These values are configured by Lagom automatically under the configuration key db.default.async-executor.

db.default {
  async-executor {
### number of objects that can be queued by the async executor
    queueSize = 10000
### 5 * number of cores
    numThreads = 20
### same as number of threads
    minConnections = 20
### same as number of threads
    maxConnections = 20
  }
}

If you haven't changed the settings for your async-executor, you have nothing to do. However, if you have configured your aync-executor with other values, you should review it and make sure that maxThreads == maxConnections.

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.4 milestone.

Updating a Lagom project to version 1.4.4

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.

v1.4.3

Compare Source

Due to a mistake during the release process this release can be ignored. It's exactly the same as 1.4.2.

v1.4.2

Compare Source

This release provides a few bug fixes and minor improvements over what 1.3.11 provides already (see the summary above). As an overview, this release contains the following:

  • Adds the message timestamp on the Kafka Message when using metadata-rich subscriptions. (#​1277)
  • Fixes a bug preventing conflicts between persistence backends when writing tests with mixed persistence (applies only to java API). ( #​1263)
  • Added a timeout on the offset polling when starting a read-side to prevent a potential read-side block in certain failure scenarios. #​1278

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.2 milestone.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with the release 1.4.2:

commits  added  removed
      9     291      56 Ignasi Marimon-Clos
      6     176     139 Tim Moore
      1      23       5 Renato Cavalcanti
      1      12       0 Jason Pickens

v1.4.1

Compare Source

This release provides a few bug fixes and minor improvements. As an overview, this release contains the following:

  • Updates Akka Persistence Cassandra to 0.60, which updates the bundled Cassandra version to 3.11.2. This fixes a crash on startup when using JDK versions 1.8.0_161 and later. (#​1204)
  • Updates Akka to 2.5.11 (also includes changes from 2.5.10).
  • Updates Play to 2.6.12.
  • Prevents SaveSnapshotSuccess from showing up in unhandled messages. (#​1209)

See GitHub for the full list of commits and the issues and pull requests assigned to the 1.4.1 milestone.

Updating a Lagom project to version 1.4.1

To update an sbt project, change the version of lagom-sbt-plugin in your project/plugins.sbt file.

To update a Maven project, change the lagom.version property in your top-level pom.xml.

After updating, it is recommended to fix any new deprecation warnings you see when compiling or running your services.

Credits

Thanks to the community for their detailed bug reports and contributions.

Thanks to Lightbend for their continued sponsorship of the Lagom core team's efforts. Lightbend offers commercial support for Lagom.

Special thanks to the following contributors who helped with this release:

commits  added  removed
      6     87       60  Tim Moore
      3     54      123  Renato Cavalcanti
      1     31        7  Lutz Huehnken

  • If you want to rebase/retry this PR, click this checkbox.

@mend-for-jackfan.us.kg mend-for-jackfan.us.kg bot added the security fix Security fix generated by WhiteSource label May 5, 2022
@mend-for-jackfan.us.kg mend-for-jackfan.us.kg bot changed the title Update dependency com.lightbend.lagom:lagom-javadsl-testkit_2.11 to v1.5.5 Update dependency com.lightbend.lagom:lagom-javadsl-testkit_2.11 to v1.5.5 - abandoned Jun 20, 2023
@mend-for-jackfan.us.kg
Copy link
Author

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security fix Security fix generated by WhiteSource
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants